Add "<LangVersion>latest</LangVersion>" to the csproj to get more useful features like pattern matching and raw string literals.

You can add dependencies, it's just important, that you also add the dependencies to the project where the source generator is used:

SourceGenerator.csproj:

  <ProjectReference Include="..\Dependency.csproj" />

FinalProject.csproj:

  <ProjectReference Include="..\Dependency.csproj" OutputItemType="Analyzer" ReferenceOutputAssembly="false" />
  <ProjectReference Include="..\SourceGenerator.csproj" OutputItemType="Analyzer" ReferenceOutputAssembly="false" />

And I also recommend to add "<LangVersion>latest</LangVersion>" to SourceGenerator.csproj to use new features like raw string literals.

Maoni Stephens is indeed on the .net team and is, as far as I know, the lead architect of the .net garbabe collector for many years: https://github.com/Maoni0 https://devblogs.microsoft.com/dotnet/author/maoni/

Therefore she's probably the person with the most knowledge about the .net GC but maybe not the best writer (I haven't read the article yet).

The writing itself is fine, but she’s assuming a LOT of knowledge e.g. what a GC0 budget is and what increasing it means.

I did not even know Server GC was a thing.

Did it get you curious enough to go look that up?

It did indeed! :D

Great! Same here. It was a great read overall. My current use-case won't benefit from DATAS (using Azure App Service), it's good to know this option exists though.

Actually, thinking about this more, this is super helpful for Stage VMs that are shared among multiple projects. It can help pack more instances in those VMs.