Note that there are some explanatory texts on larger screens.

plurals
  1. POWhat steps do I need to take to migrate to Razor?
    primarykey
    data
    text
    <p>I have just migrated my ASP.NET MVC 2 to ASP.NET MVC 3 and now I am looking into migrating from ASPX to Razor.</p> <p>The first step I have made is to use this fine code : <a href="https://stackoverflow.com/questions/4422881/aspx-to-razor-syntax-converter">Aspx to Razor syntax converter?</a></p> <p>This worked great but when running my project I get Exception like this : </p> <pre><code>Parser Error Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately. Parser Error Message: Only Content controls are allowed directly in a content page that contains Content controls. Source Error: Line 1: @{ Page Title="" Language="C#" MasterPageFile="~/Views/Shared/MasterPages/DefaultMasterPage.Master" Inherits="System.Web.Mvc.ViewPage&lt;MyApp.Views.ViewClasses.AdList&gt;" } Line 2: @using MyApp.Views.Helpers Line 3: </code></pre> <p>And my files is still named aspx, I also notice that my massterpages is not converted at all so I will probably need to do this manually.</p> <p>What steps do I need to take to get this working again? Is there anywhere to turn on the razor engine?</p> <p><strong>Note :</strong> Using Visual Studio 2012 RC</p> <p><strong>Edit :</strong> Used this tool to upgrade to ASP.NET MVC 3 : ASP.NET MVC 3 Application Upgrader <a href="http://aspnet.codeplex.com/releases/view/59008" rel="nofollow noreferrer">http://aspnet.codeplex.com/releases/view/59008</a></p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload