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
Rework the wiki #6383
base: main
Are you sure you want to change the base?
Rework the wiki #6383
Conversation
docs/wiki.md
Outdated
|
||
## Install Instructions | ||
You can download the FXCop live code analyzers as a [NuGet package](https://www.nuget.org/packages/Microsoft.CodeAnalysis.FxCopAnalyzers/) or as a Visual Studio extension ([VS2017](https://marketplace.visualstudio.com/items?itemName=VisualStudioPlatformTeam.MicrosoftCodeAnalysis2017) or [VS2019](https://marketplace.visualstudio.com/items?itemName=VisualStudioPlatformTeam.MicrosoftCodeAnalysis2019)). | ||
We've rebuilt the most popular FxCop rules and additional more rules as live analyzers to help you detect problems in your code and make it super easy for you to fix them on the spot with quick fixes. You can get the analyzers via [`Microsoft.CodeAnalysis.NetAnalyzers` NuGet package](https://www.nuget.org/packages/Microsoft.CodeAnalysis.NetAnalyzers) or from the .NET SDK. This gives you the same great code analysis as before with FXCop but now the analysis is live as-you-type and has quick-fixes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should avoid mentioning specific NuGet package, or .NET SDK or any acquisition modes here and instead just add a help link to https://learn.microsoft.com/dotnet/fundamentals/code-analysis/overview?tabs=net-7 which has all the relevant information.
docs/wiki.md
Outdated
## Apply a Code Fix for a Rule | ||
Place your cursor in the span of the squiggle/dotted line and press `Ctrl+.` to trigger the lightbulb menu. From the lightbulb, you will see all available quick actions. | ||
> Note: not all 100 code analysis rules in this extension have fixes associated with them. | ||
## Install instructions |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Again, I think we should avoid repeating Install related information in our wiki as it is already covered in .NET code analysis docs.
docs/wiki.md
Outdated
|
||
## Apply a code fix for a rule | ||
|
||
Place your cursor in the span of the squiggle/dotted line and press `Ctrl+.` to trigger the lightbulb menu. From the lightbulb, you will see all available quick actions. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please avoid all the text here and instead just add a help link to https://learn.microsoft.com/visualstudio/ide/quick-actions
For easier review, the first commit is an exact port of https://github.com/dotnet/roslyn-analyzers/wiki.
Later commits are the changes done to the Wiki.
If this PR gets merged, https://github.com/dotnet/roslyn-analyzers/wiki will need to be updated to only have a single link to the wiki in the repository.
You can also choose to close the PR and move these changes directly to the Wiki.
The benefit of having this as part of the repository is to enable community contributions.
Fixes #5234