MVC 3 View engine Razor and comparision!

Benefits over Razor are

1. Can be hosted outside ASP.NET
2. Can unit test views (no need of controller or web-server)
3. Better intellesense support on VS.NET
4. Everything is encoded by default
5. Executing it from a console app is possible
6. Much cleaner
7. There’s no need to specify the language, because it’s included in the extension
8. No need to explicitly specify a master page
9. No external dependencies as it has been shipped with MVC 3 (System.Web.Mvc.dll)
10. and lot more

Below are the urls you could enjoy reading over the major 4 view engines, it’s awesome. Just including here as it would help some one over there.

1. http://channel9.msdn.com/coding4fun/articles/Developer-Review-Four-ASPNET-MVC-View-Engines
2. http://ironshay.com/post/The-Big-View-Engine-Comparison-e28093-Razor-vs-Spark-vs-NHaml-vs-Web-Forms-View-Engine.aspx

Advertisements

Asp.Net MVC project “The project type is not supported by this installation”

One of my team members experienced this issue and was trying all the tricks got from googling, but those are all did not helped him great. After some time, we got a clue from one of the tips and verified System.Web.Mvc version in the project file.

<Reference Include=”System.Web.Mvc, Version=3.0.0.0,…>

We use VS.NET 2010. He had only System.Web.MVC 2.0 installed in his machine but the above entry was showing version 3.0. Then right away we installed MVC 3.0 and tried opening the solution. Wow…it’s worked like a charm.

Hence, if you see System.Web.Mvc Version=2.0.0.0, make sure you have MVC 2.0 installed. Likewise if see Version=3.0.0.0, make sure MVC 3.0 installed. That’s it  🙂