-
Notifications
You must be signed in to change notification settings - Fork 467
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sharp edges when CentralPackageTransitivePinningEnabled=true
in source generator projects
#7460
Comments
This is a very unlikely course for us to be taking. The guidance for .NET is pushing the ecosystem into using CPM and transitive pinning because it a much easier system for managing dependencies. There is nothing special about source generators that would lead us to giving different guidance here.
The root problem here is that your analyzer / generator ended up taking a dependency on a version of System.Collections.Immutable that was higher than what the compiler used. I can see us wanting thinking about a warning for that as it does represent a likely issue in your build. |
Of course! Just to clarify, I didn't mean to suggest a warning about CPM/CPTPE, but more so that due to a CPTPE-induced dependency version change, an additional artifact needs to be packed into For the time-being, I've just slapped So the alternative is that I could pack the bumped dependencies into my NuGet package, but there's not much guidance on how that might affect things for consumers. I haven't seen much about this in the analyzer/generator design docs, but I assume there's a reason they don't recommend shipping analyzer/generator packages fully self-contained with all in
+1 ¹( |
This isn't necessarily a bug, but it had me stumped all morning, so wanted to flag it for future readers, and maybe for the Roslyn team to consider a diagnostic warning as part of
EnforceExtendedAnalyzerRules
.Basically, turning on
CentralPackageTransitivePinningEnabled
caused our source generators to fail in Rider and Visual Studio (e.g.unable to find System.Collections.Immutable
), but notably they did not fail when runningdotnet build
.The source generators in question are bare bones and only depend on
Microsoft.CodeAnalysis.CSharp
so it took a while to realize thatCentralPackageTransitivePinningEnabled
was causing our source generator package to include a reference (but not as a dependency!) to the RC version ofSystem.Collections.Immutable
instead of the compiler-and-IDE-safe reference that usually flows fromMicrosoft.CodeAnalysis.CSharp
.So again, not a bug since this is exactly what
CentralPackageTransitivePinningEnabled
is supposed to do, but was a confusing triage given how source generator failures are displayed in the IDEs.What might be nice is a meta-analyzer to warn you when a source generator project has
CentralPackageTransitivePinningEnabled=true
. In a perfect world, this meta-analyzer would only warn whenCentralPackageTransitivePinningEnabled=true
and one of the project's transitive dependencies was actually being pinned, but not sure if the analyzer would have sufficient context for that.edit: including a target that can be dropped into the csproj and does this in a less icky way
edit: continuing to update this for future readers...
The text was updated successfully, but these errors were encountered: