Skip to main content

Viewing Generated Code

Source generators produce code at compile time. This guide explains how to view and debug generated files in different development environments.

Before You Start​

  • .NET 10.0
  • A project using Excalibur.Dispatch source generators: 
    dotnet add package Excalibur.Dispatch.SourceGenerators.Analyzers
  • Familiarity with source generators

MSBuild Configuration​

Add these properties to your .csproj to persist generated files to disk:

<PropertyGroup>
    <!-- Emit generated files to disk -->
    <EmitCompilerGeneratedFiles>true</EmitCompilerGeneratedFiles>

    <!-- Location for generated files (defaults to obj/Generated) -->
    <CompilerGeneratedFilesOutputPath>$(BaseIntermediateOutputPath)\GeneratedFiles</CompilerGeneratedFilesOutputPath>
</PropertyGroup>

After building, generated files appear in:

obj/
└── Debug/
    └── net10.0/
        └── GeneratedFiles/
            └── Excalibur.Dispatch.SourceGenerators/
                ├── CacheInfoExtractor.g.cs
                ├── CacheInfoRegistry.g.cs
                ├── DiscoveredMessageTypeMetadata.g.cs
                ├── DiscoveredMessageTypeRegistry.g.cs
                ├── EventMetadataContent.g.cs
                ├── EventStoreTypeMap.g.cs
                ├── FluentValidationDispatcher.g.cs
                ├── GeneratedHandlerActivatorRegistrations.g.cs
                ├── GeneratedHandlerRegistrationExtensions.g.cs
                ├── GeneratedSagaRegistrationExtensions.g.cs
                ├── GeneratedServiceCollectionExtensions.g.cs
                ├── HandlerInvokerRegistry.g.cs
                ├── MiddlewareDecomposition.g.cs
                ├── MiddlewareInvokers.g.cs
                ├── PipelineMetadata.g.cs
                ├── PrecompiledDirectActionDispatch.g.cs
                ├── PrecompiledHandlerMetadata.g.cs
                ├── PrecompiledHandlerRegistry.g.cs
                ├── PrecompiledSagaMetadata.g.cs
                ├── ProjectionTagResolverRegistry.g.cs
                ├── ResultFactoryRegistry.g.cs
                ├── StaticPipelines.g.cs
                ├── TypedDispatchExtensions.g.cs
                └── *Validator.g.cs (one per validated type)

Visual Studio​

  1. Expand your project in Solution Explorer
  2. Expand Dependencies → Analyzers → Excalibur.Dispatch.SourceGenerators
  3. Generated files appear as children of the generator

The generated files appear under the Analyzers node in Solution Explorer.

Method 2: Generated Files on Disk​

  1. Add MSBuild configuration above
  2. Build the project
  3. Navigate to obj/Debug/net10.0/GeneratedFiles/
  4. Open files directly

Method 3: Go to Definition​

  1. Right-click on a generated type (e.g., PrecompiledHandlerRegistry)
  2. Select Go to Definition (F12)
  3. Visual Studio opens the generated source

Debugging Generated Code​

  1. Set EmitCompilerGeneratedFiles to true
  2. Open the generated .g.cs file
  3. Set breakpoints normally
  4. Run with debugging (F5)
tip

Generated code supports full debugging including step-through, watch expressions, and conditional breakpoints.

JetBrains Rider​

Method 1: Generated Files Node​

  1. In Solution Explorer, expand your project
  2. Find the Generated folder under the project
  3. Expand Excalibur.Dispatch.SourceGenerators
  4. Browse generated files

Method 2: Navigate to Sources​

  1. Place cursor on a generated type
  2. Press Ctrl+Click or Ctrl+B
  3. Rider navigates to the generated source

Method 3: Find Usages​

  1. Right-click on a generated type
  2. Select Find Usages (Alt+F7)
  3. See all references to generated code

Rider Settings​

For better source generator experience:

  1. File → Settings → Build, Execution, Deployment → Toolset and Build
  2. Enable Use RoslynAnalyzers
  3. Enable Include source generators in code analysis

VS Code with C# Dev Kit​

Method 1: Explorer View​

  1. Install C# Dev Kit extension
  2. Open project folder
  3. After build, navigate to obj/GeneratedFiles/ in Explorer

Method 2: OmniSharp Configuration​

Create or edit .omnisharp.json in your solution root:

{
    "RoslynExtensionsOptions": {
        "EnableAnalyzersSupport": true,
        "EnableImportCompletion": true
    },
    "FormattingOptions": {
        "EnableEditorConfigSupport": true
    }
}

Method 3: Go to Definition​

  1. Hover over a generated type
  2. Ctrl+Click to navigate
  3. VS Code shows generated source in read-only mode
  • C# Dev Kit - Full C# language support
  • C# - OmniSharp-based language support
  • Solution Explorer - Visual Studio-like project tree

File Naming Conventions​

Dispatch generators use consistent naming:

GeneratorOutput File(s)Description
HandlerRegistrySourceGeneratorPrecompiledHandlerRegistry.g.cs, PrecompiledHandlerMetadata.g.cs, GeneratedHandlerRegistrationExtensions.g.cs, GeneratedHandlerActivatorRegistrations.g.cs, PrecompiledDirectActionDispatch.g.csHandler registrations, metadata, activators, and direct-action dispatch
DispatchActionExtensionGeneratorTypedDispatchExtensions.g.csTyped dispatch with TResponse inference
HandlerInvokerSourceGeneratorHandlerInvokerRegistry.g.csHandler invocation registry
MessageTypeSourceGeneratorGeneratedMessageTypeRegistrations.g.csMessage type registrations
MessageResultExtractorGeneratorResultFactoryRegistry.g.csResult factory registry for message result extraction
StaticPipelineGeneratorStaticPipelines.g.csStatic pipelines
MiddlewareDecompositionAnalyzerMiddlewareDecomposition.g.csMiddleware analysis
MiddlewareInvokerInterceptorGeneratorMiddlewareInvokers.g.csMiddleware invoker interceptors
CachePolicySourceGeneratorCacheInfoRegistry.g.csCache policies
CacheInfoSourceGeneratorCacheInfoExtractor.g.csCache info extraction
ProjectionTagResolverGeneratorProjectionTagResolverRegistry.g.csProjection cache tag resolution
ServiceRegistrationSourceGeneratorGeneratedServiceCollectionExtensions.g.csDI registrations
EventStoreTypeMapGeneratorEventStoreTypeMap.g.cs, EventMetadataContent.g.csEvent store type mappings and metadata
JsonSerializationSourceGeneratorDiscoveredMessageTypeRegistry.g.cs, DiscoveredMessageTypeMetadata.g.csJSON serialization message type discovery
FluentValidationGeneratorFluentValidationDispatcher.g.csFluent validation integration
AotValidationGenerator*Validator.g.csAOT-compatible validators (one per validated type)
SagaRegistrationGeneratorGeneratedSagaRegistrationExtensions.g.csSaga DI registrations
SagaMetadataGeneratorPrecompiledSagaMetadata.g.csSaga metadata
PipelineDeterminismAnalyzerPipelineMetadata.g.csPipeline determinism analysis metadata

When Files Regenerate​

Generated files are recreated when:

  • Project is built (full or incremental)
  • Source files change that affect generator input
  • Generator package version changes
  • Clean/rebuild is performed
Incremental Generators

Dispatch uses incremental generators that only regenerate when relevant source changes. This ensures fast build times even with many generators.

Troubleshooting​

Files Not Appearing​

  1. Check package reference:

    <PackageReference Include="Excalibur.Dispatch.SourceGenerators" Version="..." OutputItemType="Analyzer" ReferenceOutputAssembly="false" />

  2. Clean and rebuild:

    dotnet clean
    dotnet build

  3. Check build output:

    dotnet build -v:detailed 2>&1 | grep -i generator

Files Are Empty​

  1. Ensure handler interfaces are from the Excalibur.Dispatch.Delivery namespace
  2. Verify classes are public and non-abstract
  3. Check for compilation errors that block generator execution

IDE Not Showing Generated Files​

  1. Restart IDE after adding MSBuild configuration
  2. Ensure project builds successfully
  3. Check IDE-specific settings (see sections above)

Stale Generated Code​

If generated code seems outdated:

  1. Clean solution: dotnet clean
  2. Delete obj/ and bin/ folders
  3. Rebuild: dotnet build
  4. Restart IDE

Comparing Generated Output​

To compare generated output across builds:

# Save current state
cp -r obj/Debug/net10.0/GeneratedFiles ./generated-before

# Make changes and rebuild
dotnet build

# Compare
diff -r ./generated-before obj/Debug/net10.0/GeneratedFiles

CI/CD Considerations​

For build verification:

# GitHub Actions example
- name: Build and verify generators
  run: |
    dotnet build -p:EmitCompilerGeneratedFiles=true
    ls -la obj/Debug/net10.0/GeneratedFiles/Excalibur.Dispatch.SourceGenerators/

Generated files should NOT be committed to source control - they're build artifacts.

See Also​