Unexpected behavior when Source Generator access external dll

[lxymahatma]

Unexpected behavior when Source Generator access external dll

[CyrusNajmabadi]

Note: we do this in the IDE for huge memory savings. In the IDE we have hte compilation objects just reference each other, without any emitting of IL/Metadata.

The command line doesn't do this at all. When you build, it biulds, and it produces all those dlls (and all that IO). What it produces is fed into the next compiler.

This is ok on the command line (people don't mind seconds or minutes of compile costs when tey make a change). it's not ok in the IDE. People make a change and expect it to be incorporated, globally, immediately.

[jaredpar]

Looks like a dupe of #73269

[jaredpar]

In short generators are not guaranteed to see private members in external assemblies. That may happen when run in VS but will not when run through the command line. That is due to a combination of factors (ref assemblies and metadata import options) and these behaviors are by design.

[lxymahatma]

In short generators are not guaranteed to see private members in external assemblies. That may happen when run in VS but will not when run through the command line. That is due to a combination of factors (ref assemblies and metadata import options) and these behaviors are by design.

oh.. I thought since source generator cannot access private members in external libraries, the different behavior in debug and inside project is unexpected and is a bug
Cz like it's still a bit weird that you cannot access it, but in project it actually generate the files but can't get compiled. I thought it's a bug because i supposed it should be completely disabled

[jaredpar]

It's more an artifact of the different way the IDE handles references compared to the command line. It would be ideal if there was the same behavior but each environment has different constraints they are working with.

[lxymahatma]

It's more an artifact of the different way the IDE handles references compared to the command line. It would be ideal if there was the same behavior but each environment has different constraints they are working with.

Ah i see, then i guess I'll just wait for future improvements. Thank you for the detailed answer 👍🏻