Updated CarTrackr to ASP.NET MVC RC

Edit on GitHub

image As you may have noticed, ASP.NET MVC 1.0 Release Candidate has been released over the night. You can read all about it in ScottGu’s blog post, covering all new tools that have been released with the RC.

Since I’ve been trying to maintain a small reference application for ASP.NET MVC known as CarTrackr, I have updated the source code to reflect some changes in the ASP.NET MVC RC. You can download it directly from the CodePlex project page at www.cartrackr.net.

Here’s what I have updated (copied from the release notes):

Specifying View Types in Page Directives

The templates for ViewPage, ViewMasterPage, and ViewUserControl (and derived types) now support language-specific generic syntax in the main directive’s Inherits attribute. For example, you can specify the following type in the @ Master directive:

[code:xml]

<%@ Master Inherits="ViewMasterPage<IMasterInfo>" %>

[/code]

An alternative approach is to add markup like the following to your page (or to the content area for a content page), although doing so should never be necessary.

[code:xml]

<mvc:ViewType runat="server" TypeName="ViewUserControl<ProductInfo>" />

[/code]

The default MVC project templates for Visual Basic and C# views have been updated to incorporate this change to the Inherits attribute. All existing views will still work. If you choose not to use the new syntax, you can still use the earlier syntax in code.

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:

[code:xml]

<Project ToolsVersion="3.5" DefaultTargets="Build" xmlns="http://schemas.microsoft.com/developer/msbuild/2003"> 
  <PropertyGroup> 
    <MvcBuildViews>true</MvcBuildViews> 
  </PropertyGroup>

[/code]

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:

1. Open the project file in a text editor.

2. Add the following element under the top-most <PropertyGroup> element:

[code:xml]

<MvcBuildViews>true</MvcBuildViews>

[/code]

3. At the end of the project file, uncomment the <Target Name="AfterBuild"> element and modify it to match the following example:

[code:xml]

<Target Name="AfterBuild" Condition="'$(MvcBuildViews)'=='true'"> 
    <AspNetCompiler VirtualPath="temp" PhysicalPath="$(ProjectDir)\..\$(ProjectName)" />
</Target>

[/code]

kick it on DotNetKicks.com

This is an imported post. It was imported from my old blog using an automated tool and may contain formatting errors and/or broken images.

Leave a Comment

avatar

2 responses

  1. Avatar for Vinay
    Vinay January 28th, 2009

    Hi Maarten,

    I just got the latest version of the code and Visifire is failing with silverlight 2.0
    I got the latest beta from their site and modified the code..

    Just wanted to let you know about it.. and thanks for sharing your code with the community

  2. Avatar for maartenba
    maartenba January 28th, 2009

    Will fix that too. Thanks for noticing!