Rules not working after update to Visual Studio 17.5.3
See original GitHub issueHello,
after update of VS 17.4 to VS 17.5.3 it seems that stylecop analyzers are not working correctly. For example I have rules 1600 1609 set to error. If i try to
- build solution from VS then only errors 1600 is shown. If I solve it then build works (and it shouldn’t since there is still error 1609.
- build solution from command line
dotnet build
then 1600 and 1609 errors are shown.
Before update to VS 17.5.3 it all worked as expected. So it seems that for some errors it works as expectd but for some it stopped working (1609) in VS.
See example project in attachments. StyleCopTestConsoleApp.zip
Issue Analytics
- State:
- Created 6 months ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Visual Studio 2022 Release Notes
Get the latest features, bug fixes, and support for Visual Studio 2022 Preview. Download today.
Read more >Visual Studio 2022 Release Notes
Visual Studio 2022 version 17.5.3. released March 21st 2023. Issues Addressed in this release of 17.5.3. Removal of integrated Edge Developer Tools for ......
Read more >How to fix Visual Studio 2022 17.5 Intellisense not working
I do C# 6 MVC and Blazor Server. It's broken in both. Definitely looks like a problem with the latest update and needs...
Read more >Visual Studio 2022 17.5 Preview 3 is here!
Visual Studio 2022 17.5 Preview 3 is out and ready to install! This release continues to bring new productivity improvements for all ...
Read more >Visual Studio 2022 - 17.5 Released
We're excited to announce that Visual Studio 17.5 is now generally available. This release is full of updates that take friction out of...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hi @bjornhellander ,
sorry for late response. I tried it on my PC and on my colleague’s PC. We both updated VS to version >= 17.5.5 and it works now. Problem is gone. Thanks for your help and pointing out the origin of the problem.
@hudecekd Have you been able to try this with a recent Visual Studio version?