NextGenSoftware.OASIS.API.ONODE.BLL
1.0.4
dotnet add package NextGenSoftware.OASIS.API.ONODE.BLL --version 1.0.4
NuGet\Install-Package NextGenSoftware.OASIS.API.ONODE.BLL -Version 1.0.4
<PackageReference Include="NextGenSoftware.OASIS.API.ONODE.BLL" Version="1.0.4" />
paket add NextGenSoftware.OASIS.API.ONODE.BLL --version 1.0.4
#r "nuget: NextGenSoftware.OASIS.API.ONODE.BLL, 1.0.4"
// Install NextGenSoftware.OASIS.API.ONODE.BLL as a Cake Addin #addin nuget:?package=NextGenSoftware.OASIS.API.ONODE.BLL&version=1.0.4 // Install NextGenSoftware.OASIS.API.ONODE.BLL as a Cake Tool #tool nuget:?package=NextGenSoftware.OASIS.API.ONODE.BLL&version=1.0.4
NextGen Software WEB4 OASIS API ONODE BLL (Business Logic Layer)
This sit's at a higher level of abstraction over OASIS API Core, and acts as the main BLL (Business Logic Layer) to the OASIS API, whereas OASIS API Core is the core architecture and hosts the central managers such as ProviderManager, AvatarManager, HolonManager, etc, This package contains more higher level Managers (such as OLANDManager, MissionManager, ParksManager, MapManager, QuestManager, SEEDSManager, etc) and use cases built on top of OASIS API Core. This module also uses the OASISBootLoader to manage loading and using the OASISDNA/config for the ONODE. OASIS API Core does not use the OASISBootLoader because it is at a lower level in the stack and so interface implementions (OASIS Providers) need to be manually injected into each Manager's constructor (DI) whereas this module and the OASISBootLoader manages all of this for you via the OASISDNA.json config file. Both OASIS.API.Core.Native.Integrated.EndPoint & the REST API both use this module/package and provide a wrapper around it and are the recommeneded ways to use the OASIS API.
Initial Release targeting OASIS API v2.3.1 (Current LIVE REST version): https://api.oasisplatform.world
Full documentation and source code can be found here: https://github.com/NextGenSoftwareUK/Our-World-OASIS-API-HoloNET-HoloUnity-And-.NET-HDK
Make sure you check out the Overview and Benefits Of Building On The WEB 4 OASIS API sections above! 😃 Thank you!
Product | Versions Compatible and additional computed target framework versions. |
---|---|
.NET | net6.0 is compatible. net6.0-android was computed. net6.0-ios was computed. net6.0-maccatalyst was computed. net6.0-macos was computed. net6.0-tvos was computed. net6.0-windows was computed. net7.0 was computed. net7.0-android was computed. net7.0-ios was computed. net7.0-maccatalyst was computed. net7.0-macos was computed. net7.0-tvos was computed. net7.0-windows was computed. net8.0 was computed. net8.0-android was computed. net8.0-browser was computed. net8.0-ios was computed. net8.0-maccatalyst was computed. net8.0-macos was computed. net8.0-tvos was computed. net8.0-windows was computed. |
-
net6.0
- NextGenSoftware.OASIS.API.COSMIC (>= 1.0.1)
- NextGenSoftware.OASIS.OASISBootLoader (>= 1.0.5)
NuGet packages (1)
Showing the top 1 NuGet packages that depend on NextGenSoftware.OASIS.API.ONODE.BLL:
Package | Downloads |
---|---|
NextGenSoftware.OASIS.API.Native.Integrated.EndPoint
The OASIS API Native Integrated EndPoint. To be used to integrate the OASIS API directly into target applications (including Unity) instead of using the existing REST API. Can be used for offline/poor connection use cases, etc. This version will also of course be faster than the REST API. This version also contains some functionality not currently implemented in the REST API. |
GitHub repositories
This package is not used by any popular GitHub repositories.
Updated Tags