Telerik blogs

In the previous post we discussed how you could quickly create a new Visual Studio project, configured to use the Telerik Extensions for ASP.NET MVC targeting ASP.NET MVC 3. In this one, we are going to talk about how our Visual Studio Extensions have improved in regards to ASP.NET MVC 3 and the Razor view engine.

 

A significant amount of the settings the Project Configuration Wizard manages are applied to your master page. In cases where an appropriate master page has not been found, you will be prompted to create a new one:

 

convertBlog

 

If your project targets ASP.NET MVC 3, you will be offered an additional choice for your preferred view engine. Depending on you choice, you will receive either an ASPX master page, named Site.master

sitemasterblog

 

or if you select the Razor view engine, a layout page named _Layout.cshtml(vbhtml).

layoutcshtmlblog

Needless to say all of the choices you make will be applied in either case.

 

Some of you might have decided to use both view engines, because you do not want to rewrite all of your views, but don’t want to miss out on the new goodness that is Razor, If that is your case, you might have gone and created both Razor and ASPX master pages.

 

If that is your case, we are happy to let you know, the Project Configuration Wizard now supports configuring both your Site.master and _Layout.cshtml(vbhtml) pages.

 

configurebothblog

You can choose to configure either one or both.

Please, comment and share your thoughts.

Cheers,


About the Author

Erjan Gavalji

 is Software Developer in Telerik

Related Posts

Comments

Comments are disabled in preview mode.