RazorGenerator Wiki Rss Feed

Updated Wiki: Home

davidebbo — Sat, 04 May 2013 14:09:02 GMT

Razor Generator

This is a Custom Tool for Visual Studio that allows processing Razor files at design time instead of runtime, allowing them to be built into an assembly for simpler reuse and distribution.

Note that this tool currently only supports C#. VB support could probably be done if someone wants to help out with it!

Installation instructions

It’s on the VS extension gallery, so install it from there. It’s called “Razor Generator” (not to be confused with “Razor Single File Generator for MVC”).

Generator Types

MvcHelper: Creates a static type that is best suited for writing Mvc specific helper methods.
MvcView: Create a WebViewPage which allows the use of precompiled MVC views.
WebPage: Creates a WebPage type that can be used as WebPages Application Part (such as _Admin and RazorDebugger).
WebPagesHelper: Creates a HelperPage type that is suited for precompiling and distributing WebPages helper.
Template: Generator based on T4 preprocessed template.

Usage in an MVC app

Install the 'RazorGenerator.Mvc' package, which registers a special view engine
Go to an MVC Razor view's property and set the Custom tool to RazorGenerator
Optionally specify a value for Custom Tool Namespace to specify a namespace for the generated file. The project namespace is used by default.
Optionally specify one of the generators in the first line of your Razor file. A generator declaration line looks like this: @* Generator: MvcHelper *@ . If you don't specify this, a generator is picked based on convention (e.g. files under Views are treated as MvcViews)
You'll see a generated .cs file under the .cshtml file, which will be used at runtime instead of the .cshtml file
You can also go to the nuget Package Manager Console and run 'Enable-RazorGenerator' to enable the Custom Tool on all the views.
And to cause all the views to be regenerated, go to the nuget Package Manager Console and run 'Redo-RazorGenerator'. This is useful when you update the generator package and it needs to generate different code.

Usage in a View Library

If you need to create a separate library for your precompiled MVC views, the best approach is to actually create an MVC project for that library, instead of a library project. You'll never actually run it as an Mvc app, but the fact that it comes with the right set of config files allows intellisense and other things to work a lot better than in a library project.

You can then add a reference to that 'MVC View project' from your real MVC app.

And note that you need to install the 'RazorGenerator.Mvc' package into the library, not the main MVC app.

See https://github.com/davidebbo/MvcApplicationRazorGeneratorSeparateLibrary for a sample.

Special Razor directives

These directives go at the top of the cshtml file.

disabling line pragmas

@* DisableLinePragmas: true *@

Using absolute paths in line pragmas instead of relative

@* GenerateAbsolutePathLinePragmas: true *@

History

5/4/2013 Runtime v2.0.1

Fixed regression https://razorgenerator.codeplex.com/workitem/107

4/25/2013

v2.0: All the runtime assemblies are now signed.
View activation process unification https://razorgenerator.codeplex.com/workitem/105

10/14/2012

Version 1.5 of the VSIX adds support for Razor 2.0 syntax. It auto detects whether it should use 1.0 or 2.0 based on the assembly being referenced by the project.

4/20/2012

Version 1.4 of RazorGenerator.Mvc issue with multiple registered view engines (http://razorgenerator.codeplex.com/workitem/55), adds support for overriding the layout page when returning ViewResults and fixes a bug in UsePhysicalViewsIfNewer

1/8/2012

Version 1.2.3 of the VSIX fixes MVC4 issue (http://razorgenerator.codeplex.com/workitem/26)
Version 1.3.1 of RazorGenerator.Testing fixes an issue with RenderAsHtml not flowing the context

1.2 (8/29/2011)

Renamed all packages to be RazorGenerator.*
Fix issue http://razorgenerator.codeplex.com/workitem/22 (Line pragmas should not use absolute paths)

1.1.2 (8/4/2011)

Fixed encoding issue when using ANSI (non UTF-8) razor files (http://razorgenerator.codeplex.com/workitem/15)
Support null values in simple template scenario. e.g. @foo when foo is null now renders empty string. (http://razorgenerator.codeplex.com/workitem/16)

1.1.1 (7/11/2011)

Change the generated file extensions from foo.cs to foo.generated.cs (http://razorgenerator.codeplex.com/workitem/8)

1.1 (7/7/2011)

The generator now finds imported namespaces defined in web.config
Add support for project level directives in a razorgenerator.directives file

1.0.1 (6/21/2011)

Fix generated line pragmas

1.0

Original release

Updated Wiki: Home

davidebbo — Fri, 26 Apr 2013 05:28:49 GMT

Razor Generator

Installation instructions

It’s on the VS extension gallery, so install it from there. It’s called “Razor Generator” (not to be confused with “Razor Single File Generator for MVC”).

Generator Types

MvcHelper: Creates a static type that is best suited for writing Mvc specific helper methods.
MvcView: Create a WebViewPage which allows the use of precompiled MVC views.
WebPage: Creates a WebPage type that can be used as WebPages Application Part (such as _Admin and RazorDebugger).
WebPagesHelper: Creates a HelperPage type that is suited for precompiling and distributing WebPages helper.
Template: Generator based on T4 preprocessed template.

Usage in an MVC app

Install the 'RazorGenerator.Mvc' package, which registers a special view engine
Go to an MVC Razor view's property and set the Custom tool to RazorGenerator
Optionally specify a value for Custom Tool Namespace to specify a namespace for the generated file. The project namespace is used by default.
Optionally specify one of the generators in the first line of your Razor file. A generator declaration line looks like this: @* Generator: MvcHelper *@ . If you don't specify this, a generator is picked based on convention (e.g. files under Views are treated as MvcViews)
You'll see a generated .cs file under the .cshtml file, which will be used at runtime instead of the .cshtml file
You can also go to the nuget Package Manager Console and run 'Enable-RazorGenerator' to enable the Custom Tool on all the views.
And to cause all the views to be regenerated, go to the nuget Package Manager Console and run 'Redo-RazorGenerator'. This is useful when you update the generator package and it needs to generate different code.

Usage in a View Library

Special Razor directives

These directives go at the top of the cshtml file.

disabling line pragmas

@* DisableLinePragmas: true *@

Using absolute paths in line pragmas instead of relative

@* GenerateAbsolutePathLinePragmas: true *@

History

4/25/2013

v2.0: All the runtime assemblies are now signed.
View activation process unification https://razorgenerator.codeplex.com/workitem/105

10/14/2012

Version 1.5 of the VSIX adds support for Razor 2.0 syntax. It auto detects whether it should use 1.0 or 2.0 based on the assembly being referenced by the project.

4/20/2012

Version 1.4 of RazorGenerator.Mvc issue with multiple registered view engines (http://razorgenerator.codeplex.com/workitem/55), adds support for overriding the layout page when returning ViewResults and fixes a bug in UsePhysicalViewsIfNewer

1/8/2012

Version 1.2.3 of the VSIX fixes MVC4 issue (http://razorgenerator.codeplex.com/workitem/26)
Version 1.3.1 of RazorGenerator.Testing fixes an issue with RenderAsHtml not flowing the context

1.2 (8/29/2011)

Renamed all packages to be RazorGenerator.*
Fix issue http://razorgenerator.codeplex.com/workitem/22 (Line pragmas should not use absolute paths)

1.1.2 (8/4/2011)

Fixed encoding issue when using ANSI (non UTF-8) razor files (http://razorgenerator.codeplex.com/workitem/15)
Support null values in simple template scenario. e.g. @foo when foo is null now renders empty string. (http://razorgenerator.codeplex.com/workitem/16)

1.1.1 (7/11/2011)

Change the generated file extensions from foo.cs to foo.generated.cs (http://razorgenerator.codeplex.com/workitem/8)

1.1 (7/7/2011)

The generator now finds imported namespaces defined in web.config
Add support for project level directives in a razorgenerator.directives file

1.0.1 (6/21/2011)

Fix generated line pragmas

1.0

Original release

New Comment on "Using RazorGenerator.MsBuild"

gangelo — Fri, 26 Apr 2013 00:36:45 GMT

Crap instructions.

New Comment on "Using RazorGenerator.MsBuild"

thecubical — Tue, 12 Feb 2013 01:05:17 GMT

The import is slightly incorrect it should be <Import Project="$(SolutionDir)\packages\RazorGenerator.MsBuild.1.5.0.0\tools\RazorGenerator.targets"/> The version is missing the 0.0

Updated Wiki: Using RazorGenerator.MsBuild

pranavkm — Wed, 19 Dec 2012 18:12:06 GMT

Installing the package

To use the package, install the package using NuGet.

Install-Package RazorGenerator.MsBuild

If you have NuGet Package Restore enabled, the package will wire up the the target file for you. This is done by adding an import to the package restore target file.

Enabling the target without NuGet Package restore

If you do not have package restore enabled, you'll need to

a) Import the RazorGenerator.target file in your application
<Import Project="$(SolutionDir)\packages\RazorGenerator.MsBuild.1.5\tools\RazorGenerator.targets"/>

b) Add a property to your project
<PrecompileRazorFiles>true</PrecompileRazorFiles>

Verifying if it works

To verify that the Msbuild target has been set up correctly, check if files are being generated under the obj\CodeGen directory of your application.

Customizing the target

The target file assumes some default values for properties and itemgroups. These values can be overridden from your csproj

RazorSrcFiles - ItemGroup - the files that the generator precompiles. Defaults to any cshtml file under the project's directory. For instance, to customize it to only include files under the Views directory, add this ItemGroup(http://msdn.microsoft.com/en-us/library/646dk05y%28v=VS.80%29.aspx) to your csproj.

<ItemGroup>
    <RazorSrcFiles Include="Views\**\*.cshtml" />
</ItemGroup>

RazorViewsCodeGenDirectory- the directory at which files are precompiled to. Defalts to obj/CodeGen directory. You can change this by specifying a value for this property from your csproj

<RazorViewsCodeGenDirectory>$(Temp)\Myproject\RazorTempFiles\/<RazorViewsCodeGenDirectory>

Note: Property and Item group declarations must occur before the msbuild target Import

Updated Wiki: Using RazorGenerator.MsBuild

pranavkm — Wed, 19 Dec 2012 18:11:53 GMT

Installing the package

Enabling the target without NuGet Package restore

Verifying if it works

To verify that the Msbuild target has been set up correctly, check if files are being generated under the obj\CodeGen directory of your application.

Customizing the target

The target file assumes some default values for properties and itemgroups. These values can be overridden from your csproj

RazorSrcFiles - ItemGroup - the files that the generator precompiles. Defaults to any cshtml file under the project's directory. For instance, to customize it to only include files under the Views directory, add this ItemGroup(http://msdn.microsoft.com/en-us/library/646dk05y%28v=VS.80%29.aspx) to your csproj.

<ItemGroup>
    <RazorSrcFiles Include="Views\**\*.cshtml" />
</ItemGroup>

RazorViewsCodeGenDirectory- the directory at which files are precompiled to. Defalts to obj/CodeGen directory. You can change this by specifying a value for this property from your csproj

<RazorViewsCodeGenDirectory>$(Temp)\Myproject\RazorTempFiles\/<RazorViewsCodeGenDirectory>

Note: Property and Item group declarations must occur before the msbuild target Import

Updated Wiki: Using RazorGenerator.Mvc

pranavkm — Mon, 12 Nov 2012 16:31:39 GMT

To consume precompiled views from your Mvc application, you would need to install the RazorGenerator.Mvc package.

Install-Package RazorGenerator.Mvc

How it works

Views generated by the precompiled views contain a PageVirtualPath attribute that records the VirtualPath they correspond to. These values are constructed from the relative paths of the cshtml files under the Views directory.
The package adds a pre-application start hook via the type RazorGeneratorMvcStart to include a ViewEngine to the Mvc's list of engines.

var engine = new PrecompiledMvcEngine(typeof(RazorGeneratorMvcStart).Assembly) 
{
    UsePhysicalViewsIfNewer = HttpContext.Current.Request.IsLocal
};

ViewEngines.Engines.Insert(0, engine);

Configuring the PrecompiledMvcEngine

By default, the PrecompiledViewEngine registers itself as the first ViewEngine to intercept Mvc's calls for View lookups. Consequently, if a virtual path collides with another ViewEngine's, then the precompiled engine wins. For example, if your Mvc application and your precompiled application have a View at ~/Home/Index.cshtml, the precompiled view wins. You can change this behavior by having the PrecompiledMvcEngine appear later in the ViewEngines list.

ViewEngines.Engines.Add(engine);

Mvc treats Layout files and ViewStart files a bit differently than regular View files. Their lookup is done via the VirtualPathFactoryManager. To support this, our view engine implements the IVirtualPathFactory interface and registers itself during AppStart.

    // StartPage lookups are done by WebPages. 
VirtualPathFactoryManager.RegisterVirtualPathFactory(engine);

Unlike the ViewEngine scenario, we choose to do the opposite with Layout and ViewStart files: if the path of a _ViewStart file or a Layout file exists both in your precompiled assembly and your Mvc application, we'll choose the one in your Mvc application.

You can change this behavior by setting the PreemptPhysicalFiles to true on your engine:

engine.PreemptPhysicalFiles = true;

To facilitate a simpler design time experience, the ViewEngine uses physical files if they are newer than the precompiled assembly. This is to avoid having to rebuild your assembly every time you make changes to your view file. You can turn off this behavior (or make it more complex), by changing this line of code:

UsePhysicalViewsIfNewer = HttpContext.Current.Request.IsLocal

Updated Wiki: Using RazorGenerator.Mvc

pranavkm — Mon, 12 Nov 2012 16:26:26 GMT

To consume precompiled views from your Mvc application, you would need to install the RazorGenerator.Mvc package.

Install-Package RazorGenerator.Mvc

How it works

var engine = new PrecompiledMvcEngine(typeof(RazorGeneratorMvcStart).Assembly) 
{
    UsePhysicalViewsIfNewer = HttpContext.Current.Request.IsLocal
};

ViewEngines.Engines.Insert(0, engine);

Configuring the PrecompiledMvcEngine

Be the first ViewEngine to intercept Mvc's calls to look for Views. Consequently, if a virtual path collides with another ViewEngine's, then the precompiled engine wins. For example, if your Mvc application and your precompiled application have a View at ~/Home/Index.cshtml, the precompiled view wins. You can change this behavior by having the PrecompiledMvcEngine appear later in the ViewEngines list.

ViewEngines.Engines.Add(engine);

Mvc treats Layout files and ViewStart files a bit differently than regular View files. Their lookup is done via the VirtualPathFactoryManager. To support this, our view engine implements the IVirtualPathFactory interface and registers itself during AppStart.

    // StartPage lookups are done by WebPages. 
VirtualPathFactoryManager.RegisterVirtualPathFactory(engine);

engine.PreemptPhysicalFiles = true;

To facilitate a simpler design time experience, the ViewEngine uses physical files if they are newer than the precompiled assembly. This is to avoid having to rebuild your assembly every time you make changes to your view file. You can turn off this behavior (or make it more complex), by changing this line of code:

UsePhysicalViewsIfNewer = HttpContext.Current.Request.IsLocal

Updated Wiki: Documentation

pranavkm — Mon, 12 Nov 2012 16:25:50 GMT

Updated Wiki: Using RazorGenerator.Mvc

pranavkm — Mon, 12 Nov 2012 16:25:35 GMT

To consume precompiled views from your Mvc application, you would need to install the RazorGenerator.Mvc package.

Install-Package RazorGenerator.Mvc

How it works

            var engine = new PrecompiledMvcEngine(typeof(RazorGeneratorMvcStart).Assembly) 
            {
                UsePhysicalViewsIfNewer = HttpContext.Current.Request.IsLocal
            };

            ViewEngines.Engines.Insert(0, engine);

Configuring the PrecompiledMvcEngine

Be the first ViewEngine to intercept Mvc's calls to look for Views. Consequently, if a virtual path collides with another ViewEngine's, then the precompiled engine wins. For example, if your Mvc application and your precompiled application have a View at ~/Home/Index.cshtml, the precompiled view wins. You can change this behavior by having the PrecompiledMvcEngine appear later in the ViewEngines list.

         ViewEngines.Engines.Add(engine);

Mvc treats Layout files and ViewStart files a bit differently than regular View files. Their lookup is done via the VirtualPathFactoryManager. To support this, our view engine implements the IVirtualPathFactory interface and registers itself during AppStart.

    // StartPage lookups are done by WebPages. 
    VirtualPathFactoryManager.RegisterVirtualPathFactory(engine);

    engine.PreemptPhysicalFiles = true;

To facilitate a simpler design time experience, the ViewEngine uses physical files if they are newer than the precompiled assembly. This is to avoid having to rebuild your assembly every time you make changes to your view file. You can turn off this behavior (or make it more complex), by changing this line of code:

        UsePhysicalViewsIfNewer = HttpContext.Current.Request.IsLocal

Updated Wiki: Using RazorGenerator.Mvc

pranavkm — Mon, 12 Nov 2012 16:25:05 GMT

To consume precompiled views from your Mvc application, you would need to install the RazorGenerator.Mvc package.

Install-Package RazorGenerator.Mvc

How it works

            var engine = new PrecompiledMvcEngine(typeof(RazorGeneratorMvcStart).Assembly) {
                UsePhysicalViewsIfNewer = HttpContext.Current.Request.IsLocal
            };

            ViewEngines.Engines.Insert(0, engine);

Configuring the PrecompiledMvcEngine

Be the first ViewEngine to intercept Mvc's calls to look for Views. Consequently, if a virtual path collides with another ViewEngine's, then the precompiled engine wins. For example, if your Mvc application and your precompiled application have a View at ~/Home/Index.cshtml, the precompiled view wins. You can change this behavior by having the PrecompiledMvcEngine appear later in the ViewEngines list.

         ViewEngines.Engines.Add(engine);

Mvc treats Layout files and ViewStart files a bit differently than regular View files. Their lookup is done via the VirtualPathFactoryManager. To support this, our view engine implements the IVirtualPathFactory interface and registers itself during AppStart.

    // StartPage lookups are done by WebPages. 
    VirtualPathFactoryManager.RegisterVirtualPathFactory(engine);

    engine.PreemptPhysicalFiles = true;

To facilitate a simpler design time experience, the ViewEngine uses physical files if they are newer than the precompiled assembly. This is to avoid having to rebuild your assembly every time you make changes to your view file. You can turn off this behavior (or make it more complex), by changing this line of code:

        UsePhysicalViewsIfNewer = HttpContext.Current.Request.IsLocal

Updated Wiki: Using RazorGenerator.MsBuild

pranavkm — Thu, 08 Nov 2012 20:11:48 GMT

Unlike the Vsix which depends on Visual Studio's single file generator tooling, RazorGenerator.MsBuild allows precompiling views independent of Visual Studio. It works by dynamically generating C# files for Views during build which are then compiled like ordinary files in the project.

To use the package, install the package using NuGet.

Install-Package RazorGenerator.MsBuild

If you have NuGet Package Restore enabled, the package will wire up the the target file for you. This is done by adding an import to the package restore target file.

If you do not have package restore enabled, you'll need to

a) Import the RazorGenerator.target file in your application
<Import Project="$(SolutionDir)\packages\RazorGenerator.MsBuild.1.5\tools\RazorGenerator.targets"/>

b) Add a property to your project
<PrecompileRazorFiles>true</PrecompileRazorFiles>

To verify that the Msbuild target has been set up correctly, check if files are being generated under the obj\CodeGen directory of your application.

Updated Wiki: Documentation

pranavkm — Thu, 08 Nov 2012 03:17:30 GMT

Updated Wiki: Using RazorGenerator.MsBuild

pranavkm — Thu, 08 Nov 2012 03:17:15 GMT

Unlike the Vsix which depends on Visual Studio's single file generator tooling, RazorGenerator.MsBuild allows precompiling views independent of Visual Studio. It works by dynamically generating C# files for Views during build which are then compiled like ordinary files in the project.

To use the package, install the package using NuGet.

Install-Package RazorGenerator.MsBuild

If you have NuGet Package Restore enabled, the package will wire up the the target file for you. This is done by adding an import to the package restore target file.

If you do not have package restore enabled, you'll need to

a) Import the RazorGenerator.target file in your application
<Import Project="$(SolutionDir)\packages\RazorGenerator.MsBuild.1.5\tools\RazorGenerator.msbuild"/>

b) Add a property to your project
<PrecompileRazorFiles>true</PrecompileRazorFiles>

To verify that the Msbuild target has been set up correctly, check if files are being generated under the obj\CodeGen directory of your application.

Updated Wiki: Using RazorGenerator.MsBuild

pranavkm — Thu, 08 Nov 2012 03:16:48 GMT

Unlike the Vsix which depends on Visual Studio's single file generator tooling, RazorGenerator.MsBuild allows precompiling views independent of Visual Studio. It works by dynamically generating C# files for Views during build which are then compiled like ordinary files in the project.

To use the package, install the package using NuGet.

Install-Package RazorGenerator.MsBuild

If you have NuGet Package Restore enabled, the package will wire up the the target file for you. This is done by adding an import to the package restore target file.

If you do not have package restore enabled, you'll need to

a) Import the RazorGenerator.target file in your application
<Import Project="$(SolutionDir)\packages\RazorGenerator.MsBuild.1.5\tools\RazorGenerator.msbuild"/>

b) Add a property to your project
<PrecompileRazorFiles>true</PrecompileRazorFiles>

To verify that the Msbuild target has been set up correctly, check if files are being generated under the obj\CodeGen directory of your application.

Updated Wiki: Home

davidebbo — Wed, 17 Oct 2012 05:16:14 GMT

Razor Generator

Installation instructions

It’s on the VS extension gallery, so install it from there. It’s called “Razor Generator” (not to be confused with “Razor Single File Generator for MVC”).

Generator Types

MvcHelper: Creates a static type that is best suited for writing Mvc specific helper methods.
MvcView: Create a WebViewPage which allows the use of precompiled MVC views.
WebPage: Creates a WebPage type that can be used as WebPages Application Part (such as _Admin and RazorDebugger).
WebPagesHelper: Creates a HelperPage type that is suited for precompiling and distributing WebPages helper.
Template: Generator based on T4 preprocessed template.

Usage in an MVC app

Install the 'RazorGenerator.Mvc' package, which registers a special view engine
Go to an MVC Razor view's property and set the Custom tool to RazorGenerator
Optionally specify a value for Custom Tool Namespace to specify a namespace for the generated file. The project namespace is used by default.
Optionally specify one of the generators in the first line of your Razor file. A generator declaration line looks like this: @* Generator: MvcHelper *@ . If you don't specify this, a generator is picked based on convention (e.g. files under Views are treated as MvcViews)
You'll see a generated .cs file under the .cshtml file, which will be used at runtime instead of the .cshtml file
You can also go to the nuget Package Manager Console and run 'Enable-RazorGenerator' to enable the Custom Tool on all the views.
And to cause all the views to be regenerated, go to the nuget Package Manager Console and run 'Redo-RazorGenerator'. This is useful when you update the generator package and it needs to generate different code.

Usage in a View Library

Special Razor directives

These directives go at the top of the cshtml file.

disabling line pragmas

@* DisableLinePragmas: true *@

Using absolute paths in line pragmas instead of relative

@* GenerateAbsolutePathLinePragmas: true *@

History

10/14/2012

Version 1.5 of the VSIX adds support for Razor 2.0 syntax. It auto detects whether it should use 1.0 or 2.0 based on the assembly being referenced by the project.

4/20/2012

Version 1.4 of RazorGenerator.Mvc issue with multiple registered view engines (http://razorgenerator.codeplex.com/workitem/55), adds support for overriding the layout page when returning ViewResults and fixes a bug in UsePhysicalViewsIfNewer

1/8/2012

Version 1.2.3 of the VSIX fixes MVC4 issue (http://razorgenerator.codeplex.com/workitem/26)
Version 1.3.1 of RazorGenerator.Testing fixes an issue with RenderAsHtml not flowing the context

1.2 (8/29/2011)

Renamed all packages to be RazorGenerator.*
Fix issue http://razorgenerator.codeplex.com/workitem/22 (Line pragmas should not use absolute paths)

1.1.2 (8/4/2011)

Fixed encoding issue when using ANSI (non UTF-8) razor files (http://razorgenerator.codeplex.com/workitem/15)
Support null values in simple template scenario. e.g. @foo when foo is null now renders empty string. (http://razorgenerator.codeplex.com/workitem/16)

1.1.1 (7/11/2011)

Change the generated file extensions from foo.cs to foo.generated.cs (http://razorgenerator.codeplex.com/workitem/8)

1.1 (7/7/2011)

The generator now finds imported namespaces defined in web.config
Add support for project level directives in a razorgenerator.directives file

1.0.1 (6/21/2011)

Fix generated line pragmas

1.0

Original release

Updated Wiki: Home

davidebbo — Wed, 05 Sep 2012 17:58:15 GMT

Razor Generator

Installation instructions

It’s on the VS extension gallery, so install it from there. It’s called “Razor Generator” (not to be confused with “Razor Single File Generator for MVC”).

Generator Types

MvcHelper: Creates a static type that is best suited for writing Mvc specific helper methods.
MvcView: Create a WebViewPage which allows the use of precompiled MVC views.
WebPage: Creates a WebPage type that can be used as WebPages Application Part (such as _Admin and RazorDebugger).
WebPagesHelper: Creates a HelperPage type that is suited for precompiling and distributing WebPages helper.
Template: Generator based on T4 preprocessed template.

Usage in an MVC app

Install the 'RazorGenerator.Mvc' package, which registers a special view engine
Go to an MVC Razor view's property and set the Custom tool to RazorGenerator
Optionally specify a value for Custom Tool Namespace to specify a namespace for the generated file. The project namespace is used by default.
Optionally specify one of the generators in the first line of your Razor file. A generator declaration line looks like this: @* Generator: MvcHelper *@ . If you don't specify this, a generator is picked based on convention (e.g. files under Views are treated as MvcViews)
You'll see a generated .cs file under the .cshtml file, which will be used at runtime instead of the .cshtml file
You can also go to the nuget Package Manager Console and run 'Enable-RazorGenerator' to enable the Custom Tool on all the views.
And to cause all the views to be regenerated, go to the nuget Package Manager Console and run 'Redo-RazorGenerator'. This is useful when you update the generator package and it needs to generate different code.

Usage in a View Library

Special Razor directives

These directives go at the top of the cshtml file.

disabling line pragmas

@* DisableLinePragmas: true *@

Using absolute paths in line pragmas instead of relative

@* GenerateAbsolutePathLinePragmas: true *@

History

4/20/2012

Version 1.4 of RazorGenerator.Mvc issue with multiple registered view engines (http://razorgenerator.codeplex.com/workitem/55), adds support for overriding the layout page when returning ViewResults and fixes a bug in UsePhysicalViewsIfNewer

1/8/2012

Version 1.2.3 of the VSIX fixes MVC4 issue (http://razorgenerator.codeplex.com/workitem/26)
Version 1.3.1 of RazorGenerator.Testing fixes an issue with RenderAsHtml not flowing the context

1.2 (8/29/2011)

Renamed all packages to be RazorGenerator.*
Fix issue http://razorgenerator.codeplex.com/workitem/22 (Line pragmas should not use absolute paths)

1.1.2 (8/4/2011)

Fixed encoding issue when using ANSI (non UTF-8) razor files (http://razorgenerator.codeplex.com/workitem/15)
Support null values in simple template scenario. e.g. @foo when foo is null now renders empty string. (http://razorgenerator.codeplex.com/workitem/16)

1.1.1 (7/11/2011)

Change the generated file extensions from foo.cs to foo.generated.cs (http://razorgenerator.codeplex.com/workitem/8)

1.1 (7/7/2011)

The generator now finds imported namespaces defined in web.config
Add support for project level directives in a razorgenerator.directives file

1.0.1 (6/21/2011)

Fix generated line pragmas

1.0

Original release

Updated Wiki: Home

davidebbo — Fri, 03 Aug 2012 00:27:53 GMT

Razor Generator

Installation instructions

It’s on the VS extension gallery, so install it from there. It’s called “Razor Generator” (not to be confused with “Razor Single File Generator for MVC”).

Generator Types

MvcHelper: Creates a static type that is best suited for writing Mvc specific helper methods.
MvcView: Create a WebViewPage which allows the use of precompiled MVC views.
WebPage: Creates a WebPage type that can be used as WebPages Application Part (such as _Admin and RazorDebugger).
WebPagesHelper: Creates a HelperPage type that is suited for precompiling and distributing WebPages helper.
Template: Generator based on T4 preprocessed template.

Usage in an MVC app

Install the 'RazorGenerator.Mvc' package, which registers a special view engine
Go to an MVC Razor view's property and set the Custom tool to RazorGenerator
Optionally specify a value for Custom Tool Namespace to specify a namespace for the generated file. The project namespace is used by default.
Optionally specify one of the generators in the first line of your Razor file. A generator declaration line looks like this: @* Generator: MvcHelper *@ . If you don't specify this, a generator is picked based on convention (e.g. files under Views are treated as MvcViews)
You'll see a generated .cs file under the .cshtml file, which will be used at runtime instead of the .cshtml file
You can also go to the nuget Package Manager Console and run 'Enable-RazorGenerator' to enable the Custom Tool on all the views.
And to cause all the views to be regenerated, go to the nuget Package Manager Console and run 'Redo-RazorGenerator'. This is useful when you update the generator package and it needs to generate different code.

Usage in a View Library

History

4/20/2012

Version 1.4 of RazorGenerator.Mvc issue with multiple registered view engines (http://razorgenerator.codeplex.com/workitem/55), adds support for overriding the layout page when returning ViewResults and fixes a bug in UsePhysicalViewsIfNewer

1/8/2012

Version 1.2.3 of the VSIX fixes MVC4 issue (http://razorgenerator.codeplex.com/workitem/26)
Version 1.3.1 of RazorGenerator.Testing fixes an issue with RenderAsHtml not flowing the context

1.2 (8/29/2011)

Renamed all packages to be RazorGenerator.*
Fix issue http://razorgenerator.codeplex.com/workitem/22 (Line pragmas should not use absolute paths)

1.1.2 (8/4/2011)

Fixed encoding issue when using ANSI (non UTF-8) razor files (http://razorgenerator.codeplex.com/workitem/15)
Support null values in simple template scenario. e.g. @foo when foo is null now renders empty string. (http://razorgenerator.codeplex.com/workitem/16)

1.1.1 (7/11/2011)

Change the generated file extensions from foo.cs to foo.generated.cs (http://razorgenerator.codeplex.com/workitem/8)

1.1 (7/7/2011)

The generator now finds imported namespaces defined in web.config
Add support for project level directives in a razorgenerator.directives file

1.0.1 (6/21/2011)

Fix generated line pragmas

1.0

Original release

Updated Wiki: Home

pranavkm — Fri, 20 Apr 2012 16:22:19 GMT

Razor Generator

This is a Custom Tool for Visual Studio that allows processing Razor files at design time instead of runtime, allowing them to be built into an assembly for simpler reuse and distribution.

Installation instructions

It’s on the VS extension gallery, so install it from there. It’s called “Razor Generator” (not to be confused with “Razor Single File Generator for MVC”).

Generator Types

MvcHelper: Creates a static type that is best suited for writing Mvc specific helper methods.
MvcView: Create a WebViewPage which allows the use of precompiled MVC views.
WebPage: Creates a WebPage type that can be used as WebPages Application Part (such as _Admin and RazorDebugger).
WebPagesHelper: Creates a HelperPage type that is suited for precompiling and distributing WebPages helper.
Template: Generator based on T4 preprocessed template.

Usage in an MVC app

Install the 'RazorGenerator.Mvc' package, which registers a special view engine
Go to an MVC Razor view's property and set the Custom tool to RazorGenerator
Optionally specify a value for Custom Tool Namespace to specify a namespace for the generated file. The project namespace is used by default.
Optionally specify one of the generators in the first line of your Razor file. A generator declaration line looks like this: @* Generator: MvcHelper *@ . If you don't specify this, a generator is picked based on convention (e.g. files under Views are treated as MvcViews)
You'll see a generated .cs file under the .cshtml file, which will be used at runtime instead of the .cshtml file
You can also go to the nuget Package Manager Console and run 'Enable-RazorGenerator' to enable the Custom Tool on all the views.
And to cause all the views to be regenerated, go to the nuget Package Manager Console and run 'Redo-RazorGenerator'. This is useful when you update the generator package and it needs to generate different code.

Usage in a View Library

History

4/20/2012

Version 1.4 of RazorGenerator.Mvc issue with multiple registered view engines (http://razorgenerator.codeplex.com/workitem/55), adds support for overriding the layout page when returning ViewResults and fixes a bug in UsePhysicalViewsIfNewer

1/8/2012

Version 1.2.3 of the VSIX fixes MVC4 issue (http://razorgenerator.codeplex.com/workitem/26)
Version 1.3.1 of RazorGenerator.Testing fixes an issue with RenderAsHtml not flowing the context

1.2 (8/29/2011)

Renamed all packages to be RazorGenerator.*
Fix issue http://razorgenerator.codeplex.com/workitem/22 (Line pragmas should not use absolute paths)

1.1.2 (8/4/2011)

Fixed encoding issue when using ANSI (non UTF-8) razor files (http://razorgenerator.codeplex.com/workitem/15)
Support null values in simple template scenario. e.g. @foo when foo is null now renders empty string. (http://razorgenerator.codeplex.com/workitem/16)

1.1.1 (7/11/2011)

Change the generated file extensions from foo.cs to foo.generated.cs (http://razorgenerator.codeplex.com/workitem/8)

1.1 (7/7/2011)

The generator now finds imported namespaces defined in web.config
Add support for project level directives in a razorgenerator.directives file

1.0.1 (6/21/2011)

Fix generated line pragmas

1.0

Original release

Updated Wiki: Home

davidebbo — Wed, 07 Mar 2012 17:33:04 GMT

Razor Generator

This is a Custom Tool for Visual Studio that allows processing Razor files at design time instead of runtime, allowing them to be built into an assembly for simpler reuse and distribution.

Installation instructions

It’s on the VS extension gallery, so install it from there. It’s called “Razor Generator” (not to be confused with “Razor Single File Generator for MVC”).

Generator Types

MvcHelper: Creates a static type that is best suited for writing Mvc specific helper methods.
MvcView: Create a WebViewPage which allows the use of precompiled MVC views.
WebPage: Creates a WebPage type that can be used as WebPages Application Part (such as _Admin and RazorDebugger).
WebPagesHelper: Creates a HelperPage type that is suited for precompiling and distributing WebPages helper.
Template: Generator based on T4 preprocessed template.

Usage in an MVC app

Install the 'RazorGenerator.Mvc' package, which registers a special view engine
Go to an MVC Razor view's property and set the Custom tool to RazorGenerator
Optionally specify a value for Custom Tool Namespace to specify a namespace for the generated file. The project namespace is used by default.
Optionally specify one of the generators in the first line of your Razor file. A generator declaration line looks like this: @* Generator: MvcHelper *@ . If you don't specify this, a generator is picked based on convention (e.g. files under Views are treated as MvcViews)
You'll see a generated .cs file under the .cshtml file, which will be used at runtime instead of the .cshtml file
You can also go to the nuget Package Manager Console and run 'Enable-RazorGenerator' to enable the Custom Tool on all the views.
And to cause all the views to be regenerated, go to the nuget Package Manager Console and run 'Redo-RazorGenerator'. This is useful when you update the generator package and it needs to generate different code.

Usage in a View Library

History

1/8/2012

Version 1.2.3 of the VSIX fixes MVC4 issue (http://razorgenerator.codeplex.com/workitem/26)
Version 1.3.1 of RazorGenerator.Testing fixes an issue with RenderAsHtml not flowing the context

1.2 (8/29/2011)

Renamed all packages to be RazorGenerator.*
Fix issue http://razorgenerator.codeplex.com/workitem/22 (Line pragmas should not use absolute paths)

1.1.2 (8/4/2011)

Fixed encoding issue when using ANSI (non UTF-8) razor files (http://razorgenerator.codeplex.com/workitem/15)
Support null values in simple template scenario. e.g. @foo when foo is null now renders empty string. (http://razorgenerator.codeplex.com/workitem/16)

1.1.1 (7/11/2011)

Change the generated file extensions from foo.cs to foo.generated.cs (http://razorgenerator.codeplex.com/workitem/8)

1.1 (7/7/2011)

The generator now finds imported namespaces defined in web.config
Add support for project level directives in a razorgenerator.directives file

1.0.1 (6/21/2011)

Fix generated line pragmas

1.0

Original release

RazorGenerator Wiki Rss Feed

Updated Wiki: Home

Razor Generator

Installation instructions

Generator Types

Usage in an MVC app

Usage in a View Library

Special Razor directives

disabling line pragmas

Using absolute paths in line pragmas instead of relative

History

5/4/2013 Runtime v2.0.1

4/25/2013

10/14/2012

4/20/2012

1/8/2012

1.2 (8/29/2011)

1.1.2 (8/4/2011)

1.1.1 (7/11/2011)

1.1 (7/7/2011)

1.0.1 (6/21/2011)

1.0

Related blog posts:

Updated Wiki: Home

Razor Generator

Installation instructions

Generator Types

Usage in an MVC app

Usage in a View Library

Special Razor directives

disabling line pragmas

Using absolute paths in line pragmas instead of relative

History

4/25/2013

10/14/2012

4/20/2012

1/8/2012

1.2 (8/29/2011)

1.1.2 (8/4/2011)

1.1.1 (7/11/2011)

1.1 (7/7/2011)

1.0.1 (6/21/2011)

1.0

Related blog posts:

New Comment on "Using RazorGenerator.MsBuild"

New Comment on "Using RazorGenerator.MsBuild"

Updated Wiki: Using RazorGenerator.MsBuild

Installing the package

Enabling the target without NuGet Package restore

Verifying if it works

Customizing the target

Updated Wiki: Using RazorGenerator.MsBuild

Installing the package

Enabling the target without NuGet Package restore

Verifying if it works

Customizing the target

Updated Wiki: Using RazorGenerator.Mvc

How it works

Configuring the PrecompiledMvcEngine

Updated Wiki: Using RazorGenerator.Mvc

How it works

Configuring the PrecompiledMvcEngine

Updated Wiki: Documentation

Table of Contents

Updated Wiki: Using RazorGenerator.Mvc

How it works

Configuring the PrecompiledMvcEngine

Updated Wiki: Using RazorGenerator.Mvc

How it works

Configuring the PrecompiledMvcEngine

Updated Wiki: Using RazorGenerator.MsBuild

Updated Wiki: Documentation

Table of Contents

Updated Wiki: Using RazorGenerator.MsBuild

Updated Wiki: Using RazorGenerator.MsBuild

Updated Wiki: Home

Razor Generator

Installation instructions

Generator Types

Usage in an MVC app