How can I deploy an ASP.NET web on IIS without creating a separate site?

I've created an ASP.NET web tool that will just be used by a few people in my team where I work. I 开发者_如何学Godeployed it on our internal (Win2k, IIS6) web server by creating a new website in IIS and assigning it port 81. Users can access it with an address like http://myserver:81. All the other web stuff on the server is classic ASP and is accessed with addresses like http://myserver/path/to/myfile.asp.

This works fine, but I'd rather set it up so that the ASP.NET app is not configured as a separate web site, and is just accessed via a folder path like the classic asp stuff. That way users wouldn't have to specify the port and we wouldn't get the overhead of an additional web site for every little ASP.NET app we make.

The problem is when I build the site in visual studio, it compiles all the .cs files into one .dll file, and if I just copy everything over to some folder on the server and type the address of the .aspx file, it can't seem to access any of the c# functions in that .dll file.

Can an ASP.NET app be set up like this, short of writing all C# code within the .aspx files?

Assuming you want your application to run as a subfolder of a website bound to http://192.168.1.1:

1. Build your website, and drop it into a subfolder called "A" in the root website folder

2. Verify that Network Service and IUsr accounts have read access (at least) to your Subfolder

3. Verify that the application pool serving the website is using the same version of the .NET Framework as your application (Probably 2.0 if you're using IIS 6)

4. Verify that the application pool is running under the Network Service Identity

5. Right click the folder in IIS, and convert it to an application

6. Make sure you setup an adequate default file on the application, such as default.aspx

7. Access http://192.168.1.1/A/ and your application should load

Note: All applications in the website must run the same version of the .NET Framework