Wireloom.Dds.Generator
0.3.0
dotnet add package Wireloom.Dds.Generator --version 0.3.0
NuGet\Install-Package Wireloom.Dds.Generator -Version 0.3.0
<PackageReference Include="Wireloom.Dds.Generator" Version="0.3.0" />
<PackageVersion Include="Wireloom.Dds.Generator" Version="0.3.0" />
<PackageReference Include="Wireloom.Dds.Generator" />
paket add Wireloom.Dds.Generator --version 0.3.0
#r "nuget: Wireloom.Dds.Generator, 0.3.0"
#:package Wireloom.Dds.Generator@0.3.0
#addin nuget:?package=Wireloom.Dds.Generator&version=0.3.0
#tool nuget:?package=Wireloom.Dds.Generator&version=0.3.0
Wireloom.Dds.Generator
Wireloom.Dds.Generator is a Roslyn source generator and MSBuild integration for
generating C# types from the RTI Connext DDS IDL subset. Add it to a .NET
project that owns DDS data contracts; the package generates source during the
normal build and does not invoke Java, native tooling, or rtiddsgen.
This is a preview package. Support is feature-specific and evidence-driven; successful compilation of one IDL shape is not a blanket claim of RTI or wire compatibility.
Install
Add the generator and the RTI runtime explicitly. The generator package does
not add Rti.ConnextDds transitively because the application owns its runtime
version and configuration.
<ItemGroup>
<PackageReference Include="Rti.ConnextDds" Version="7.3.1" />
<PackageReference Include="Wireloom.Dds.Generator"
Version="0.2.0"
PrivateAssets="all" />
</ItemGroup>
The retained oracle corpus was generated with RTI Connext DDS 7.7.0 /
rtiddsgen 4.7.0. The compatibility floor is RTI 7.3.1 and later because
7.3.1 ships the same rtiddsgen version. The consumer project must resolve a
compatible Rti.ConnextDds reference and use C# 12 or later.
Declare an IDL generation root
Declare each file that starts generation with a DdsIdl item:
<ItemGroup>
<DdsIdl Include="Contracts\Telemetry.idl" />
</ItemGroup>
The IDL root can include other files. Included files are tracked inputs and are not independently generated as roots.
module Telemetry {
struct Sample {
long id;
string<64> label;
sequence<float, 8> values;
};
};
The generated API follows the IDL module structure. For the example above, the
consumer can use the generated Telemetry.Sample data type and, when the
selected feature shape has type support, Telemetry.SampleSupport:
var sample = new Telemetry.Sample
{
Id = 42,
Label = "temperature",
Values = [20.5f, 21.0f]
};
var typeSupport = Telemetry.SampleSupport.Instance;
Generated types include the managed data contract and the RTI-specific support surface where the IDL shape is supported: native companions, type support, interpreted plugins, and DynamicType metadata.
Configure includes and preprocessing
Use project properties for defaults shared by roots, or root-item metadata for the project-wide generation batch:
<PropertyGroup>
<DdsIdlIncludeDirectories>
$(MSBuildProjectDirectory)\Contracts\Shared
</DdsIdlIncludeDirectories>
</PropertyGroup>
<ItemGroup>
<DdsIdl Include="Contracts\Telemetry.idl"
IncludeDirectories="$(MSBuildProjectDirectory)\Contracts\Telemetry"
Defines="ENABLE_DIAGNOSTICS;PRODUCT_VARIANT=Enterprise"
Undefines="LEGACY_LAYOUT"
Strict="true" />
</ItemGroup>
Supported metadata:
| Setting | Scope | Meaning |
|---|---|---|
DdsIdlIncludeDirectories |
Project | Semicolon-separated directories searched for configured includes and tracked for invalidation |
IncludeDirectories |
Root-item metadata collected for the batch | Additional include directories available to the generation batch |
Defines |
Root-item metadata collected for the batch | Semicolon-separated preprocessor symbols |
Undefines |
Root-item metadata collected for the batch | Semicolon-separated symbols removed before preprocessing |
Strict |
Root-item metadata collected for the batch | Enables strict validation for the generation batch when any root sets it |
The current compiler combines these settings across all generating roots. It does not provide isolated preprocessing or validation settings per root.
Quoted relative includes resolve from the including file's directory. Angle includes use the configured include directories. Keep a shared file as an included input unless it is intentionally a separate generation root.
Inspect generated source
Roslyn exposes generated documents through the IDE. To also write physical
generated files under obj, use the standard compiler options:
<PropertyGroup>
<EmitCompilerGeneratedFiles>true</EmitCompilerGeneratedFiles>
<CompilerGeneratedFilesOutputPath>$(BaseIntermediateOutputPath)generated</CompilerGeneratedFilesOutputPath>
</PropertyGroup>
The package does not create a separate command-line output directory or run a pre-generation step.
Diagnostics
| ID | Meaning | Typical action |
|---|---|---|
DDSG0001 |
IDL generation failed | Fix the source-located parse, include, semantic, or unsupported-feature error |
DDSG0002 |
C# 12 or later is required | Set the consumer's language version to C# 12 or later |
DDSG0003 |
A compatible RTI runtime was not found | Add an explicit Rti.ConnextDds reference at the tested compatible version |
DDSG0101 |
An unknown IDL annotation was ignored | Verify the annotation is supported by the managed generator if it affects the generated contract |
DDSG0102 |
A recognized but unsupported IDL annotation was ignored | Remove the annotation or use a supported declaration context |
DDSG0103 |
A non-DDS IDL interface was ignored | Use a DDS service interface when interface generation is required |
DDSG0104 |
A function-like macro was invoked with the wrong number of arguments | Correct the macro invocation; RTI-compatible expansion continues after the warning |
DDSG0105 |
A direct array of sequences may not preserve IDL semantics | Use a typedef for the sequence before declaring the array |
DDSG0106 |
An active #warning directive was encountered |
Review the warning in the IDL or included file; preprocessing and generation continue |
DDSG0107 |
An active #pragma message directive was encountered |
Review the informational message in the IDL or included file; generation continues |
Diagnostics are owned by the generator and use the original IDL/include
location where one is available. Configure severity through standard
.editorconfig entries, for example:
dotnet_diagnostic.DDSG0001.severity = error
Supported boundary
The current corpus exercises modules, structs, nested declarations, aliases, enums, unions, constants, primitive values, narrow and wide strings, bounded strings, sequences, arrays, include graphs, conditional preprocessing, keys, annotations, and extensibility. Several of these are supported only for the specific shapes covered by the retained RTI oracle evidence.
The package intentionally rejects unsupported declarations and directives instead of emitting an incomplete contract. Before adopting a feature, check the feature coverage matrix and the corpus rules.
The compatibility corpus compares source-generation behavior and generated C# shape. It does not automatically prove serialization-byte equivalence, live DDS behavior, or C++ interoperability.
What this package does not do
- It does not provide the RTI DDS runtime, transport, or serialization engine.
- It does not invoke or forward arbitrary arguments to
rtiddsgen. - It does not implicitly generate every
.idlfile in a project; roots are explicitDdsIdlitems. - It does not promise complete Connext IDL coverage or universal drop-in compatibility with RTI-generated C#.
- It does not silently omit unsupported declarations.
Troubleshooting
The generator reports DDSG0003
Add the runtime package to the consuming project. The generator package is
private build tooling; the application must reference Rti.ConnextDds itself.
An include cannot be resolved
Check whether the include is quoted or angle-bracketed. Quoted includes are
resolved relative to the including file. For angle includes, add the directory
to DdsIdlIncludeDirectories or the root's IncludeDirectories metadata.
A shared file is generated twice
Keep the shared file as an included input and declare only the intended root in
DdsIdl. A physical IDL file should normally have one generation identity per
consumer project.
A feature is rejected
Read the source-located DDSG0001 diagnostic, then check the feature coverage
matrix. Rejection is intentional when the current managed compiler does not
have evidence for a safe generated contract.
Learn more
RTI-generated reference material in the repository is retained under the applicable RTI license and review rules. It is not redistributed by this NuGet package.
Learn more about Target Frameworks and .NET Standard.
This package has no dependencies.
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.