ASP.NET MVC – Deployed on IIS6, stops loading after session start

asp.netasp.net-mvciis-6

Reaching out here… I have an ASP.NET MVC app, which runs flawlessly on VS2008 dev server and IIS7. However, deploying on IIS6 yields blank pages and no error message in event logs either. Very frustrating!

I've tried the wildcard mapping techniques, extension based routing ({controller}.aspx/{action}) and every config variation I could think of.

Does anybody have any ideas for troubleshooting a problem like this? Why would IIS serve up a blank page instead of something real (like an error). Memory issues? Machine has 4Gig of RAM, so that shouldn't be an issue.

Logging in the application shows that the Global.asax file is being processed successfully up until Session_Start. After that (when routing should take over), it stops.

Any ideas would be appreciated!

Best Answer

You have to set up some ISAPI mappings. Phil Haack covered it on his blog. You can find the entry here: http://haacked.com/archive/2008/11/26/asp.net-mvc-on-iis-6-walkthrough.aspx

It is kind of a pain, but it is the way IIS6 handles things. I am not sure if the RC version still has this problem as I am all IIS7 today.

Related Solutions

Asp.net-mvc – Can an ASP.NET MVC controller return an Image

Use the base controllers File method.

public ActionResult Image(string id)
{
    var dir = Server.MapPath("/Images");
    var path = Path.Combine(dir, id + ".jpg"); //validate the path for security or use other means to generate the path.
    return base.File(path, "image/jpeg");
}

As a note, this seems to be fairly efficient. I did a test where I requested the image through the controller (http://localhost/MyController/Image/MyImage) and through the direct URL (http://localhost/Images/MyImage.jpg) and the results were:

MVC: 7.6 milliseconds per photo
Direct: 6.7 milliseconds per photo

Note: this is the average time of a request. The average was calculated by making thousands of requests on the local machine, so the totals should not include network latency or bandwidth issues.

Asp.net-mvc – Compile Views in ASP.NET MVC

From the readme word doc for RC1 (not indexed by google)

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:

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

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:

Open the project file in a text editor.
Add the following element under the top-most <PropertyGroup> element: <MvcBuildViews>true</MvcBuildViews>
At the end of the project file, uncomment the <Target Name="AfterBuild"> element and modify it to match the following:

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

Best Answer

Related Solutions

Asp.net-mvc – Can an ASP.NET MVC controller return an Image

Asp.net-mvc – Compile Views in ASP.NET MVC

Related Topic