5

I am experimenting with C# source generators. I have spent about a day on it, and I find it a very frustrating and painful experience. IntelliSense is extremely unreliable. It occasionally works, but most often it does not, and I have not been able to figure out any system to it. (Restarting Visual Studio does not help.)

But more fundamentally, I have great trouble debugging errors in the generated code. When I make a mistake in the template in the source generator and try to compile, I might get errors like "Method must have a return type" in the generated file. But when I double-click on the error, it doesn't take me to the generated code. That makes it extremely hard to see what is wrong with it.

Is there a trick to it? Is there any way to inspect the generated code when it fails to compile? And more generally, what governs when the generated code is available for IntelliSense and when it is not?

I am using Visual Studio Professional 2022 version 17.1.6 and ReSharper 2022.1.

Thanks in advance!

Claus Appel
  • 1,015
  • 10
  • 28
  • Are you using T4 templates? – Ross Bush May 24 '22 at 13:10
  • @RossBush See the link OP included. I believe Source Generators was (were) added in .Net 5 – phuzi May 24 '22 at 13:13
  • +1. I managed to get a source generator working after fiddling with it for several hours. However, when inspecting the `obj` folder, I don't see a way I can inspect the code that is being included in the assembly. So, that is also something I would like to know. – NightOwl888 May 24 '22 at 13:19
  • `what governs when the generated code is available for IntelliSense and when it is not?` - I know the answer to that one - Intellisense is controlled by [source code analyzers](https://learn.microsoft.com/en-us/visualstudio/code-quality/roslyn-analyzers-overview?view=vs-2022). You really should limit your posts to a single question so they can be answered more easily. – NightOwl888 May 24 '22 at 13:24
  • 1
    I found [an answer to how to output source code](https://andrewlock.net/creating-a-source-generator-part-6-saving-source-generator-output-in-source-control/#emitting-compiler-generated-files) from a source generator, and it even goes into details about how to control the output path. – NightOwl888 May 25 '22 at 13:12
  • 2
    If you expand the Dependencies node in Solution Explorer, under that is Analyzers. Find your analyzer and expand it, and then expand the node representing your source generator. All your generated files should appear there. – Kirk Woll May 25 '22 at 21:31
  • Apparently that "expand Dependencies node" trick only works when the source generator compiles. If it fails to compile, it is simply not listed. – Claus Appel May 31 '22 at 19:09

2 Answers2

3

Add the following to your code generator constructor code:

#if DEBUG 
    if (!Debugger.IsAttached) 
    { 
        Debugger.Launch(); 
    } 
#endif

Now you can use breakpoints in Visual Studio.

Intellisense is indeed garbage in VS with code generators. You need to close VS, delete /bin and /obj folders, reopen VS, then rebuild. This has to be done everytime you make changes. VS will show the old version after you changed something, intellisense will mark new things as error, yet it will still compile and run...

For a better experience I recommend using Rider, which has a much better integration experience for code generators.

Skelvir
  • 41
  • 5
  • Thank you very much! I've finally gotten the debugger working. For others trying to do the same in rider, I had to set rider as the default jit debugger before getting this to work. Check [the documentation](https://jetbrains.com.xy2401.com/help/rider/Starting_Debugging.html#636ebf50) to see how you do this. – Swan Apr 03 '23 at 23:34
1

I have found a partial solution to my problem.

First, do not use the ReSharper builder in Visual Studio when working with source generators. It does not give proper error messages. Instead, run dotnet build from a command line. You'll get much better error messages that way.

In fact, part of my problem may be due to bugs or limitations in ReSharper (though I have not investigated this, so that is pure speculation).

Second, you can test the innards of your source generator without running the source generation at compile time.

  1. Refactor your source generator and extract a helper class (we can call it SourceGeneratorHelper.cs) that takes your input (e.g. XML) and produces output (e.g. a StringBuilder).
  2. Make a separate C# test project SourceGeneratorHelperTest.csproj for testing the class SourceGeneratorHelper.cs. In this project, reference your source generator project as if it were a regular project - i.e., DO NOT USE OutputItemType="Analyzer" in your project reference.
  3. Now you can unit test the innards of your source generator. You can also dump the generated C# code to a file and inspect it.

Moreover, as NightOwl888 pointed out, I can add this to the referencing project in order to get it to spit out the generated files to disk ( as explained in this article):

<PropertyGroup>
    <EmitCompilerGeneratedFiles>true</EmitCompilerGeneratedFiles>
</PropertyGroup>

I have not solved the IntelliSense problem, but now I can at least endure working with this generator.

Claus Appel
  • 1,015
  • 10
  • 28