Go to Control Panel – Programs and Features

Click “Turn Windows Features On and Off”

Select all the features as shown below.

Create a New Application for our project our Project under C:\Inetpub\wwwroot

Now we set up IIS for our application

Expand the Sites to get to our project directory

Click Basic Settings in the Action Panel

Select Classic.Net AppPool

If you are using a 64Bit Operating System you will need to allow 32 Bit application to run from your IIS.
To do so:
1. Go to the IIS Manager.
2. Open "Application Settings".
3. Select the "Application Pools" item on the tree on the left.
4. Right click on the "Classic .NET AppPool" from the list.
5. Select "Advanced Settings".
6. Change the "Enable 32-Bit Applications" setting to "True" as shown in the screenshot below.

Highlight the .ASPX handler and click Edit Script

Copy the Executable path to the clipboard
Cancel to close and click Add Script

Enter the Path as *.wgx and paste the executable copied in the previous step
Add a name eg WebGUI
Click 'OK' to Save
A box will pop up asking if you wish to allow the ISAPI extension. Click 'Yes'

This procedure will have to be repeated for all NET versions and all bitness-es you need. This example is registering a Script Map for NET2.0 32bit, but you may have to repeat the procedure for NET2.0 64bit, NET4.0 32bit and NET4.0 64bit, if those bitness-es and frameworks are needed for your application.

We are now ready to copy our files to our new application directory
This shows using Publish from VS2008 (right click your project and select Publish, then click the browse/Ellipsis button)

BEWARE
If “Delete all existing files prior to publish” is checked it will also delete the WGX handler added earlier

Now we see all the structure

BEWARE
Sometimes Publish does not copy Web.config to the root directory

Now we can run the application by pointing our browser to http://localhost/catalog64/mainform.wgx