I'm working on a project with lots of razor views (.cshtml), and after upgrading a dependency i will need to fix lots of errors.

Is there a way to prevent the compiler to not stop at the first error and instead make it so it compiles every view in the project, listing all the existing errors like it does in Jet Brains Rider?

Currently using Visual Studio 2022.

I'm working on a project with lots of razor views (.cshtml), and after upgrading a dependency i will need to fix lots of errors.

Is there a way to prevent the compiler to not stop at the first error and instead make it so it compiles every view in the project, listing all the existing errors like it does in Jet Brains Rider?

Currently using Visual Studio 2022.

• visual-studio
• razor
• visual-studio-2022
• roslyn

Share Improve this question Follow asked Nov 18, 2024 at 11:23 Leonardo T.Leonardo T. 991010 bronze badges

Add a comment  | 

1 Answer 1

Sorted by: Reset to default 0

Even when you can get a compile & link tool such as Visual Studio to carry on despite errors you run the risk of cascade errors that make it problematic to locate the actual source of the error due to the sheer volume of problem reports.

If you are looking for something to go through your code looking for potential problems and to list them all out for you then you will probably be better off running a linter. The trick of course is to find a linter that supports razor views (.cshtml) as well as your code.

• ReSharper will highlight & list potential problems from within your IDE for you. This is probably one of your best options.
• Some editions of SonarCube do support this.
• OmiSharp may have implemented this support by now.
• There may well be others.