Meshmakers.Octo.Sdk.Adapters
3.4.18
dotnet add package Meshmakers.Octo.Sdk.Adapters --version 3.4.18
NuGet\Install-Package Meshmakers.Octo.Sdk.Adapters -Version 3.4.18
<PackageReference Include="Meshmakers.Octo.Sdk.Adapters" Version="3.4.18" />
<PackageVersion Include="Meshmakers.Octo.Sdk.Adapters" Version="3.4.18" />
<PackageReference Include="Meshmakers.Octo.Sdk.Adapters" />
paket add Meshmakers.Octo.Sdk.Adapters --version 3.4.18
#r "nuget: Meshmakers.Octo.Sdk.Adapters, 3.4.18"
#:package Meshmakers.Octo.Sdk.Adapters@3.4.18
#addin nuget:?package=Meshmakers.Octo.Sdk.Adapters&version=3.4.18
#tool nuget:?package=Meshmakers.Octo.Sdk.Adapters&version=3.4.18
octo-communication-sdk
OctoMesh Communication SDK — the adapter framework, ETL pipeline, and runtime infrastructure used to build adapter services that connect external systems to the OctoMesh platform.
This repository was carved out of octo-sdk in Phase 3 of the YAML pipeline migration. The split separates the client SDK (REST clients, contracts — stays in octo-sdk) from the adapter / pipeline infrastructure (lives here).
Layout
src/
├── Sdk.Adapters/ — adapter base classes (was Sdk.Common/Adapters)
├── Sdk.Pipeline/ — ETL pipeline + node framework + execution services
│ (was Sdk.Common/EtlDataPipeline + Sdk.Common/Services)
├── Sdk.CommunicationAdapter/ — Generic Host + DI bootstrap for hosting adapters
├── Sdk.Plug.Simulation/ — sample simulation adapter
└── Sdk.SimulationNodes/ — pipeline-node implementations for simulation
Dependency direction
octo-distributedEventHub
↓
octo-construction-kit-engine
↓
octo-sdk (Communication.Contracts, Sdk.ServiceClient, Sdk.Common/Encryption stay here)
↓
octo-common-services
↓
octo-communication-sdk ← this repo
↓
(consumers: mesh-adapter, eda-adapter, loxone, mqtt, sap, finapi,
modbus, demos, communication-controller-services, communication-operator)
Build
# Production
dotnet build Octo.CommunicationSdk.sln -c Release
# Local dev (reads NuGets from ../nuget — populated by `invoke-buildall -configuration DebugL`)
dotnet build Octo.CommunicationSdk.sln -c DebugL
Release
Releases are driven by release-communication-train.yml in octo-mesh-deployment (Phase 5 of the migration). The train tags r<X.Y.Z> on this repo and queues the CI on the tag. Versioning follows the A2 Layered strategy: this repo carries its own version line (comm-X.Y.Z) and pins to a Libs major-minor via OctoVersion in Directory.Build.props.
See also
- Architecture concept:
octo-mesh-deployment/docs/pipeline-architecture-concept.md - Original SDK: octo-sdk
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net10.0 is compatible. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
-
net10.0
- Meshmakers.Octo.Common.DistributionEventHub (>= 3.4.16)
- Meshmakers.Octo.Communication.Contracts (>= 3.4.16)
- Meshmakers.Octo.ConstructionKit.Contracts (>= 3.4.16)
- Meshmakers.Octo.Sdk.Common (>= 3.4.16)
- Meshmakers.Octo.Sdk.Pipeline (>= 3.4.18)
- Meshmakers.Octo.Sdk.ServiceClient (>= 3.4.16)
- Microsoft.Extensions.Configuration (>= 10.0.9)
- Microsoft.Extensions.DependencyInjection (>= 10.0.9)
- Microsoft.Extensions.Hosting (>= 10.0.9)
- Microsoft.Extensions.Logging (>= 10.0.9)
- Microsoft.Extensions.Options (>= 10.0.9)
- NLog (>= 6.1.3)
- NLog.Extensions.Logging (>= 6.1.3)
NuGet packages (2)
Showing the top 2 NuGet packages that depend on Meshmakers.Octo.Sdk.Adapters:
| Package | Downloads |
|---|---|
|
Meshmakers.Octo.Sdk.Common.Web
Package to create AspNetcore based sockets and plugs Octo Mesh |
|
|
Meshmakers.Octo.Sdk.MeshAdapter
Mesh adapter SDK to create custom mesh adapters |
GitHub repositories
This package is not used by any popular GitHub repositories.