This week I spent some time deploying a Web application I developed using Microsoft Visual Web Developer 2010 Express (it’s free). For that, I installed Microsoft Internet Information Service (IIS) on my Windows 7 enterprise edition. This turned out pretty straight-forward: Control Panel – Programs – Turn Windows Features on or off. In the Windows Features dialog box, just locate the Internet Information Service and check on it. After a click on the OK button, the IIS (version/build is IIS 7.5.7600.16385) was installed.
But it didn’t work for my ASP.Net Web application. To run it, I had to go through extra steps. I figure I would probably set up an IIS server on other servers later, therefore better document it for future. To make it simple, I omitted the error messages and how I researched the issues. It would be great if you also find it helpful.
Bothered by SLOW Web UI to manage vSphere? Want to manage ALL your VMware vCenters, AWS, Azure, Openstack, container behind a SINGLE pane of glass? Want to search, analyze, report, visualize VMs, hosts, networks, datastores, events as easily as Google the Web? Find out more about vSearch 3.0: the search engine for all your private and public clouds.
Here are extra steps after the default installation:
- By default, ASP.Net is not turned on. I had to go back to the Windows Features dialog box and click down the Internet Information Service – World Wide Web Services – Application Development Features. There are several items including ASP.Net. To make it simple, I just checked them all.
- Afterward, I got an issue with targetFramework value in the Web.config. My Web application defaults it to 4.0, but it’s not recognized. To fix that, open the IIS manager (just type in inetmgr upon clicking Start). Click on the Application Pools in the left side tree, then double click DefaultAppPool. In the Edit Application Pool dialog box, from the .Net Framework version dropdown list, pick .Net Framework v4.0.30319.
- It still didn’t work. It turned out that ASP.Net needs to be registered per this article. Running the following two commands should do the trick.
%windir%\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe -i %windir%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe –i
You need to change the path to the specific versions of .NET on your machine.