I created an ASP.NET web tool that will be used by several people in my team where I work. I deployed it to our internal (Win2k, IIS6) web server, creating a new website in IIS and assigning port 81 to it. Users can access it with an address, for example http: // myserver: 81 . All other websites on the server are classic ASPs and are accessible with addresses such as http: //myserver/path/to/myfile.asp .
This works fine, but I would prefer to configure it so that the ASP.NET application is not configured as a separate website and is accessible only through the folder path, such as the classic asp material. This way, users would not need to specify a port, and we would not get the overhead of an additional website for every small ASP.NET application we make.
The problem is when I create a site in visual studio, it compiles all .cs files into one. A DLL file, and if I just copy everything to some folder on the server and type in the address of the .aspx file, it cannot access any of the C # functions in this DLL file.
Is it possible to configure an ASP.NET application so that it does not write all the C # code inside the .aspx files?
source
share