Get IIS to run Quickly

[joe_pool_is]

I need to get IIS running on 2 separate test machines.

 

One PC has been in the company for several years. When I Opened the IIS Console, I saw there was a website called "Sales Portal" running, using ASP.NET Version 1.0, and the IP Address under the identification was not reachable through PING. I *guess* this PC has a lot of old data that isn't even used anymore.

 

The other PC has nothing set, but IIS is installed.

 

I need to do testing on these two machines, and I'd like to know the fastest way of getting this done.

 

Should I uninstall IIS on the old PC, then reinstall it? I'd guess that would wipe everything out, wouldn't it (Unless Microsoft doesn't clean out their registries)?

 

Next, what's the fastest way to get IIS set up? I don't need anything fancy, but I would like to have different folders in C:\Inetpub\wwwroot so that I can test pages for different customers without removing one that is existing.

 

Can this be done? I need ASP.NET to run in most of them.

 

For Example:

C:
  Inetpub
        wwwroot
              TestSite1
                    Default.aspx
              TestSite2
                    Default.aspx
              Default.aspx

The wwwroot\Default.aspx could be anything, but I'd like to place our Customers' projects in the individual folders, and run them by browsing to "localhost/TestSite1" or "localhost/TestSite2".

 

Could someone show me a way of doing this?

 

It sounds like an awful lot to me! So, thanks to whoever takes the time to answer this.

[Diesel]

It's not as complicated as you think, IIS is really just a medium between external requests and ASP.Net.

 

Reinstalling it won't matter.

 

So, here are the assumptions Im making; the OS's are the same, and the version of IIS is the same, you want to work with .Net 2.0.

 

So, you didn't specify whether .Net 2.0 framework was installed...installing it on both machines would be the first step.

 

ASP.Net should register itself, and you can run multiple versions of ASP.Net on the same puter, so the 1.0 app is fine.

 

If ASP.Net does not register itself correctly, run the command line tool aspnet_regiis:

 

http://msdn2.microsoft.com/en-us/library/k6h9cz8h(VS.80).aspx

 

 

After that, good ol' VS2005 takes care of creating the virtual directories for you. Just create a new web site, and change the location from "File System" to "Http" and then specify something based on the localhost, ie. http://localhost/TestSite1.

 

That's it.

[joe_pool_is]

Thanks Diesel.

 

When VS2005 starts a Web Project, it sends it to something like http://localhost:1640/ and a little icon appears in the tastbar tray indicating that ASP is up and running.

 

Is there a way to do this manually so that I can open my web browser and go straight to the localhost site?

[Diesel]

Im pretty sure that little tray icon your talking about means VS starting it's built in web server....

 

Make sure when you create the website, the location type is Http, in the dropdown box next to the name.

 

When you run the website, it should not pop up a tray icon, and should just pop up the default browser. The address should not have a port number, it should be a localhost child directory; http://localhost/WebSite3/Default.aspx.

 

You can open your own browser window and type in that (your website) address. Everytime you build the solution, the files that changed will be recompiled.