tree: 8047a75e1019036016538c7f792e1fcaf3dad177 [path history] [tgz]
  1. BaSyx.AAS.Client.Http.1.0.0.nupkg
  2. BaSyx.AAS.Client.Http.1.0.0.symbols.nupkg
  3. BaSyx.AAS.Server.Http.1.0.0.nupkg
  4. BaSyx.AAS.Server.Http.1.0.0.symbols.nupkg
  5. BaSyx.API.1.0.0.nupkg
  6. BaSyx.API.1.0.0.symbols.nupkg
  7. BaSyx.API.Http.Controllers.1.0.0.nupkg
  8. BaSyx.API.Http.Controllers.1.0.0.symbols.nupkg
  9. BaSyx.API.Http.Controllers.AASX.1.0.0.nupkg
  10. BaSyx.API.Http.Controllers.AASX.1.0.0.symbols.nupkg
  11. BaSyx.Common.UI.1.0.0.nupkg
  12. BaSyx.Common.UI.1.0.0.symbols.nupkg
  13. BaSyx.Common.UI.Swagger.1.0.0.nupkg
  14. BaSyx.Common.UI.Swagger.1.0.0.symbols.nupkg
  15. BaSyx.Components.Common.1.0.0.nupkg
  16. BaSyx.Components.Common.1.0.0.symbols.nupkg
  17. BaSyx.Components.Common.Abstractions.1.0.0.nupkg
  18. BaSyx.Components.Common.Abstractions.1.0.0.symbols.nupkg
  19. BaSyx.Discovery.mDNS.1.0.0.nupkg
  20. BaSyx.Discovery.mDNS.1.0.0.symbols.nupkg
  21. BaSyx.Models.1.0.0.nupkg
  22. BaSyx.Models.1.0.0.symbols.nupkg
  23. BaSyx.Models.Export.1.0.0.nupkg
  24. BaSyx.Models.Export.1.0.0.symbols.nupkg
  25. BaSyx.Registry.Client.Http.1.0.0.nupkg
  26. BaSyx.Registry.Client.Http.1.0.0.symbols.nupkg
  27. BaSyx.Registry.ReferenceImpl.FileBased.1.0.0.nupkg
  28. BaSyx.Registry.ReferenceImpl.FileBased.1.0.0.symbols.nupkg
  29. BaSyx.Registry.Server.Http.1.0.0.nupkg
  30. BaSyx.Registry.Server.Http.1.0.0.symbols.nupkg
  31. BaSyx.Submodel.Client.Http.1.0.0.nupkg
  32. BaSyx.Submodel.Client.Http.1.0.0.symbols.nupkg
  33. BaSyx.Submodel.Server.Http.1.0.0.nupkg
  34. BaSyx.Submodel.Server.Http.1.0.0.symbols.nupkg
  35. BaSyx.Utils.1.0.0.nupkg
  36. BaSyx.Utils.1.0.0.symbols.nupkg
  37. BaSyx.Utils.Client.Mqtt.1.0.0.nupkg
  38. BaSyx.Utils.Client.Mqtt.1.0.0.symbols.nupkg
  39. BaSyx.Utils.DependencyInjection.1.0.0.nupkg
  40. BaSyx.Utils.DependencyInjection.1.0.0.symbols.nupkg
  41. BaSyx.Utils.DependencyInjection.Abstractions.1.0.0.nupkg
  42. BaSyx.Utils.DependencyInjection.Abstractions.1.0.0.symbols.nupkg
  43. Readme.md
  44. Setup_BaSyx_NuGet_Repo.bat
sdks/dotnet/basyx-packages/Readme.md

# Welcome to basyx-packages! In this repository you‘ll find all ready-to-use NuGet packages of the entire BaSyx .NET SDK. With these packages you’re ready to develop, e.g.:

  • Server Applications for
    • Asset Administration Shells & their optional Repositories,
    • Submodels & their optional Repositories,
    • Registry
  • Client Applications for
    • Asset Administration Shells,
    • Submodels,
    • Registry.
  • Middleware Components
    • Registry
    • mDNS-Discovery
  • Read & Write
    • JSON & XML serialization
    • AASX-Packages
  • and much more...

Setup

In order to access the NuGet-Packages from the dotnet environment resp. Microsoft Visual Studio, the packages folder needs to be registered as NuGet source.

Either use

Setup_BaSyx_NuGet_Repo.bat

or open command prompt in the packages folder an enter

setx BASYX_REPO %cd%
dotnet nuget add source %cd% --name BaSyx.Packages

The first command sets an user environment variable. It's necessary if you want to build the SDK on your own. Each SDK project file contains a command as post-build process that generates a new NuGet package which will be stored in the folder mentioned in BASYX_REPO environment variable.