You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a great possibility that I have misunderstood how this should work, but here we go:
Project A is a source generator.
Project A relies on additional files for its output.
Project A is packaged as a NuGet package.
Project B references project A's NuGet package.
Project B defines additional files, wich influences project A's output.
Project A's source generating code does not execute because project A's version hasn't changed and Project A's NuGet package is being cached.
Fail?
In this scenario caching of project A's NuGet package doesn't make sense in my opinion. There should at least be a mechanism to turn caching off for NuGet packages containing generators.
Any thoughts? Is there a solution for this scenario?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
There is a great possibility that I have misunderstood how this should work, but here we go:
Project A is a source generator.
Project A relies on additional files for its output.
Project A is packaged as a NuGet package.
Project B references project A's NuGet package.
Project B defines additional files, wich influences project A's output.
Project A's source generating code does not execute because project A's version hasn't changed and Project A's NuGet package is being cached.
Fail?
In this scenario caching of project A's NuGet package doesn't make sense in my opinion. There should at least be a mechanism to turn caching off for NuGet packages containing generators.
Any thoughts? Is there a solution for this scenario?
Beta Was this translation helpful? Give feedback.
All reactions