Not registered yet?
Register now! It is easy and done in 1 minute and gives you access to special discounts and much more!
By John Oxley
I want an msbuild task to compile the views so I can see if there are compile time errors at well... compile time. Any ideas?
I frankly would recommend the RazorGenerator nuget package. That way your views have a .designer.cs file generated when you save them and on top of getting compile time errors for you views, they are also precompiled into the assembly (= faster warmup) and Resharper provides some additional help as well.
To use this include the RazorGenerator nuget package in you ASP.NET MVC project and install the "Razor Generator" extension under item under Tools → Extensions and Updates.
We use this and the overhead per compile with this approach is much less. On top of this I would probably recommend .NET Demon by RedGate which further reduces compile time impact substantially.
Hope this helps.
is there a similiar solution vor VS2012?
Unfortunate that it only supports C# and no VB.Net
@zoidbergi RazorGenerator works with VS2012; when using RazorGenerator.Mvc and RazorGenerator.MsBuild: no need for extension. See blog entry on stacktoheap.com
Can this be used to only find errors - or does it replace the view engine when deploying the application?
I've installed RazorGenerator nuget package and Razor Generator extension. Nothing has been changed in my project. No .designer.cs files appeared. I use visual studio 2017.
@MichaelSamteladze Haven't tested with .NET Core and haven't done Razor in ages, but assuming you are on full framework take a look at the Razor Generator docs here: github.com/RazorGenerator/RazorGenerator Easiest is to use the Enable-RazorGenerator in the Package Manager Console. Good Luck!
@MichaelSamteladze I tried (caveat with 1 minute of investment) on core with no luck (on either pages or views) and I am not sure I would advise anyone to use ASP.NET MVC (meaning non-.Core) today if they intended to use Razor pages or views and for the app to live for a while (if greenfield) unless there is a compelling argument against Core. No idea what applies to your case.
@Mirko my project is not .NET Core, I have regular MVC5 Web Application
You can use aspnet_compiler for this:
C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet_compiler -v /Virtual/Application/Path/Or/Path/In/IIS/Metabase -p C:\Path\To\Your\WebProject -f -errorstack C:\Where\To\Put\Compiled\Site
where "/Virtual/Application/Path/Or/Path/In/IIS/Metabase" is something like this: "/MyApp" or "/lm/w3svc2/1/root/"
Also there is a AspNetCompiler Task on MSDN, showing how to integrate aspnet_compiler with MSBuild:
This is out of date, see an excerpt from the readme doc below.
The other answer describes the project task in more detail, but the aspnet_compiler portion is still correct (and useful on build agents).
Using Visual Studio's Productivity Power Tools (free) extension helps a bit. Specifically, the Solution Error Visualizer feature. With it, compilation errors marked visually in the solution explorer (in the source file where the error was found). For some reason, however, this feature does not work as with other errors anywhere else in the code.
Solution Error Visualizer
With MVC views, any compile-time errors will still be underlined in red in their respective .cs files, but signaling these errors is not propagated upwards in the Solution Explorer (in no way, even not in the containing source file).
Thanks for BlueClouds for correcting my previous statement.
I have just reported this as an issue on the extension's github project.
I tried Productivity Power Tools. But does not behave as what is said here. There is error in razor view but build is success. views are not marked or underlined in red, or anywhere in solution exploer tree.
@BlueClouds: you are right. I created a sample project and added a compile-time error in a view. The extension will underline the erroring lines in red, but will not propagate the error up in the solution explorer. Am correcting what I stated in the answer. Am leaving the answer here as it still helps a bit, while indeed not solving the problem effectively.
Build > Run Code Analysis
Hotkey : Alt+F11
Helped me catch Razor errors.
I upvoted this answer because the hotkey did indeed expose a Razor error. However I subsequently noticed that it only seems to work if you have the .cshtml file open in the IDE.
From the readme word doc for RC1 (not indexed by google)
ASP.NET Compiler Post-Build Step
Currently, errors within a view file are not detected until run time. To let you detect these errors at compile time, ASP.NET MVC projects now include an MvcBuildViews property, which is disabled by default. To enable this property, open the project file and set the MvcBuildViews property to true, as shown in the following example:
<Project ToolsVersion="3.5" DefaultTargets="Build" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
Note Enabling this feature adds some overhead to the build time.
You can update projects that were created with previous releases of MVC to include build-time validation of views by performing the following steps:
<Target Name="AfterBuild" Condition="'$(MvcBuildViews)'=='true'">
<AspNetCompiler VirtualPath="temp" PhysicalPath="$(ProjectDir)\..\$(ProjectName)" />
If this should not work for your project, check if there isn't an <MvcBuildViews>false</MvcBuildViews> somewhere in your project file. It was overriding the new <MvcBuildViews> element I added on top of it.
@mxmissile: Scott Guthrie recommended adding a Web Deployment Project to your solution to get this sort of support in Web Application Projects: weblogs.asp.net/scottgu/archive/2006/09/22/…
Make sure that EnableUpdateable is set to false or else the views wont be precompiled. <EnableUpdateable>false</EnableUpdateable> <MvcBuildViews>true</MvcBuildViews> (devcarl.posterous.com/…)
I'm having an issue with this, where a default namespace is imported in the web.config, but the pages are failing to compile, any hints?
Why, why, why...there is no keyboard shortcut for building with or without views? MS why?
This is the solution added to the MVC tools. stackoverflow.com/a/2670792/878612
For me this solution displays errors in the generated .cs files, rather than the actual errors in the .cshtml files. Is there a way to change this? It's not really "usable" this way.
It works but double clicking the error in the error list doesn't open the View - anyway to do this?
After applying the solution above, I started getting an error relating to my web.config (due to a release version existing in my obj folder). To fix that, you can remove the obj folders during the BeforeBuild phase. Source: gunnarpeipman.com/aspnet/…
The answer given here works for some MVC versions but not for others.
The simple solution worked for MVC1 but on upgrading to MVC2 the views were no longer being compliled. This was due to a bug in the website project files. See this Haacked article.
See this: http://haacked.com/archive/2011/05/09/compiling-mvc-views-in-a-build-environment.aspx
Also, if you use Resharper, you can active Solution Wide Analysis and it will detect any compiler errors you might have in aspx files. That is what we do...
It's true it works for aspx files, but the solution-wide analysis does not include ascx files (user controls)
I believe it does in R# 5, but it's a huge resource hog for large projects (even on my 16GB home machine it's not worth using).
@Andrew / @mookid8000 -- R# will also catch errors that the compiler won't, such as missing/incorrect views and actions. R# will slow your PC down a bit (I find it fine on a large-ish project with 4GB ram and a hyperthreaded CPU) but I easily make back the time I spend waiting for it, and I end up doing fewer operations on my code as R# provides higher level operations that batch together the many steps I'd have to take to achieve the same task manually. Your project must be huge!
For large projects, "slow your PC down a bit" is an understatement. My build machine has 16GB of RAM and 8 cores (2 Xeons), and it just CRAWLS. I have a feeling R# just wasn't made for projects our size though ... e.g. our solution has ~30 projects, a couple Million LOC, and many hundreds of views. I love R# on our smaller projects (e.g. a few projects and no more than 50 views), but on our big one we always have to turn it off.
This MAY work, but RUN AWAY! I turned this on thinking my solution was small and it never finished 'analyzing' and ate all my RAM and CPU. Took me 15 minutes to recover.
Next release of ASP.NET MVC (available in January or so) should have MSBuild task that compiles views, so you might want to wait.