Source Generator Intellisense

[bforl]

I have 3 projects in my solution

• A Source Generator project that generates classes
• A library project that uses the above source generator
• A console app that references the library

For some reason, intelli-sense for the source generated classes only works inside the library project?
Intelli-sense for source generated classes does not work for the console app. I can write code with them, and it will compile, but I get no ide support for them

Is this to be expected?

[huoyaoyuan]

When you made any change with source generator, you need to do a full build then restart IDE, to ensure the latest generator is loaded in IDE.
Do you still observe the IntelliSense issue after restarting?

[CyrusNajmabadi]

Intellisense is best effort with SGs. Because of our extremely tight perf requirements, it is often the case that generators haven't completed by the time semantic information is needed by a feature like completion.

We've also just had bugs in this area. Like not realizing a save of a file should rerun generators.

[bforl]

I've now tried moving the source generator to a completely different solution, building it once, and using it by dll reference. But I am getting the same issue. After changing the xml files in the Library (used by the source generator) the intellisense for the source generated code in the Lib project works, but it doesn't work in the console project :(

VS Solution 1
Source Generator

VS Solution 2
Library (references the dll by path from VS Solution 1)
Console (references the library by project reference)

I reference the analyser in the Library using the following :

<ItemGroup>
	<Analyzer Include="C:\Source\KeysSourceGenerator\KeysSourceGenerator\bin\Debug\netstandard2.0\KeysSourceGenerator.dll" />
</ItemGroup>

[bforl]

I've just noticed that it seems to work much better with VS Professional? ...previously I was using the community edition.

[jasonmalinowski]

I've just noticed that it seems to work much better with VS Professional? ...previously I was using the community edition.

Professional vs. Community edition won't matter here -- we don't change anything in this based on which edition you're using. Something else is causing that difference.

[bforl]

Hmm - ok. Not sure then. But things definitely started working better.