Deploying .NET 4.0 Application on IIS 6.0 November 21, 2010Posted by Bilal in Programming, Web.
Tags: .NET, 2.0, 4.0, asp, asp.net, C#, IIS 6, IIS7, Visual Studio
I had my ASP.NET 2.0 application hosted on Windows 2003 Sever with IIS 6.0. After Visual Studio 2010 or more precisely after .NET Framework 4.0, I upgraded the desktop modules to 4.0 (version 3.0 and 3.5 are superset, not the framework). The transition of desktop application from 2.0 to 4.0 was smooth enough. Although there were some deep level changes required in some scenarios (minor ones) but overall it was simple. The application executed properly in the first attempt.
I updated the Web Modules also but did not deploy them (in production environment only). Recently, it was planned to deploy the upgraded module. I installed the framework 4.0 on the web server and using the existing Publish settings, I published the upgraded application on the server (test server, not making experiments on the production server). On browsing the page, I got a 404 Page not found error. It was really a wired and unexpected situation. I have read about the issue of upgrading from IIS 6.0 to IIS 7.0 specially related to web.config but this transition error was totally not expected.
After a lot of search and attempts, I was able to execute the application. Below are the minimum steps required for it:
- In IIS 6 console, right click you project and click the properties and check the ASP.Net tab whether Framework 4 is selected or not. If not select the framework 4.
- In IIS 6 single application pool can’t be used for two different frameworks. Add a new pool with any meaningful name. Application Pools is above the Default
Website node in the main tree hierarchy. (IIS 7 supports)
- To assign the application pool, in IIS console open the properties section of the web application, and click on the Home Directory tab and select newly created application pool from the drop-down-list.
Basically Page not found issue is cause of other problem which is set hidden by IIS6. But you need to see the real cause.
- For this open IIS6 console and in the main hierarchy, select Web Service Extension node which is right below the Default Website node. You will see the entire ASP.Net framework list over there, by default these frameworks might be set to Prohibited so select ASP.Net Framework 4 and click Allow button.
Browse you website now and it should be working.
If you are having some other errors, check the source link.
Server.MapPath February 15, 2010Posted by Bilal in .NET, APS, C#, Microsoft, Visual Studio 2005, Visual Studio 2008.
Tags: absolute path, asp, fiel location, mapPath, relative path, server
add a comment
Server.MapPath specifies the relative or virtual path to map to a physical directory.
- Server.MapPath(“.”) returns the current physical directory of the file (e.g. aspx) being executed
- Server.MapPath(“..”) returns the parent directory
- Server.MapPath(“~”) returns the physical path to the root of the application
- Server.MapPath(“/”) returns the physical path to the root of the domain name (is not necessarily the same as the root of the application)
Let’s say you pointed a web site application (http://www.example.com/) to the root of your domain
and installed your shop application (as virtual directory in IIS and marked as application) in
If, you call Server.MapPath in following request:
- Server.MapPath(“.”) returns D:\WebApps\shop\products
- Server.MapPath(“..”) returns D:\WebApps\shop
- Server.MapPath(“~”) returns D:\WebApps\shop
- Server.MapPath(“/”) returns C:\Inetpub\wwwroot
- Server.MapPath(“/shop”) returns D:\WebApps\shop
If Path starts with either a forward (/) or backward slash (\), the MapPath method returns a path as if Path were a full, virtual path.
If Path doesn’t start with a slash, the MapPath method returns a path relative to the directory of the request being processed.
Note: In C#, @ is the verbatim literal string operator meaning that the string should be used “as is” and not be processed for escape sequences.