Clone StartupAnalyzer in to Framework analyzers

[pranavkm]

StartupAnalyzers currently ship as part of the SDK and apply to all apps targeting .NET Core 3.1 and newer. If we'd like to introduce new recommendations that specifically target 6.0, one option might be to clone it in to Framework Analyzers and leave the ones targeting the SDK alone. Another option might be to see if we're able to read the TFM inside the analyzer.

Thanks for contacting us.

We're moving this issue to the .NET 7 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

Thanks for contacting us.

We're moving this issue to the .NET 8 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[david-acker]

It sounds like this would be relevant to [Analyzer] : Warn when registering custom IProblemDetailsWriter after calling AddRazorPages, etc #48180 since this new analyzer would leverage the existing StartupAnalyzer, but IProblemDetailsWriter only exists in 7.0+.

Would it make sense to handle this first before adding the analyzer above?