Fix build when using source generators coming from NuGet packages. #6798
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #6792
Main PR #6793
Description
Fixes build of project using source generators coming from NuGet packages. I fixed this by only including analyzers that are coming from a FrameworkReference in the temporary target assembly project. Those analyzers are the ones that are not automatically added in the temporary target assembly project because ResolveTargetingPackAssets is never called (We could investigate calling this target in the future but, to me, it seemed riskier than the changes in this PR).
Customer Impact
Fixes build.
Regression
This is a regression introduced in .Net 6.0.7 by #6534 which was backported by #6680. Those were changes from me, sorry about the regression.
Testing
Tested locally by building a project which uses Regex source generator, WinForms source generator and CommunityToolkit.Mvvm 7.1.2 source generator (This is an example of a source generator that currently fails on .Net 6.0.7 SDK).
Risk
Low.
Microsoft Reviewers: Open in CodeFlow