ASP.NET 3.5 deployment issue under IIS5

asp.net-ajaxdeploymentiisiis-6

Having gone through the pain of converting an ASP.NET website project to a web application project, I am now have trouble deploying this to our live web server under IIS5.

Under my local development machine (running IIS7) the deployment is working fine. I publish the web application project in Visual Studio 2008 to a folder on my local machine and then create a new website under IIS7.

When I try to do the same (with the same deployed files) on our live server under IIS5 I get the following:

"Object reference not set to an instance of an object.

Line 1: <%@ Language="C#" MasterPageFile="~/MyMaster.master" AutoEventWireup="true" Inherits="MyMaster.index" Codebehind="index.aspx.cs" %> "

Anyone got any ideas??

Best Answer

.NET Framework 3.5 is not supported on Windows 2000.

UPDATE

If you are converting a Web Site Project to a Web Application Project make sure to check these pointers.

Related Solutions

How to deploy your ASP.NET applications to live servers

We have all of our code deployed in MSIs using Setup Factory. If something has to change we redeploy the entire solution. This sounds like overkill for a css file, but it absolutely keeps all environments in sync, and we know exactly what is in production (we deploy to all test and uat environments the same way).

Asp.net-mvc – ASP MVC in IIS 7 results in: HTTP Error 403.14 – Forbidden

Maybe it's useful to someone: After converting my app to MVC 4 with .NET framework 4.5 and installing the framework on my server with IIS 7.0 I encountered the same 'forbidden' error mentioned in the question. I tried all options described above to no avail, when I noticed the

<system.webServer>
 <modules runAllManagedModulesForAllRequests="true"/>
</system.webServer>

was missing from my web.config. After adding this, everything worked. Simple, but easy to overlook...

EDIT:

Of course the solution above will work, but it is indeed a waste of resources. I think it is better to add the routing module as pointed out by Chris Herring in the comments.

<system.webServer>
  <modules>
    <remove name="UrlRoutingModule-4.0" />
    <add name="UrlRoutingModule-4.0" type="System.Web.Routing.UrlRoutingModule" preCondition="" />
  </modules>
</system.webServer>

Best Answer

Related Solutions

How to deploy your ASP.NET applications to live servers

Asp.net-mvc – ASP MVC in IIS 7 results in: HTTP Error 403.14 – Forbidden

Related Topic