This is an outline of what happens when you use Gotham. We will assume you have gone through Installation.

Let us imagine we want to load http://localhost/test.asp into the browser. When the browser makes the request this happens:

1. IIS on localhost sees the request is for a .asp file
2. IIS looks in its configuration and see that .asp is mapped to ASP.NET
3. IIS looks in the directory for the default website, let's call it c:\inetpub\wwwroot for a file called web.config. This file contains configuatation data for the web site
4. In web.config it finds a section that tells it .asp files should be given to an Assembly called IISInterface.
5. IISInterface is really c:\inetpub\wwwroot\bin\IISInterface.dll and is a part of Gotham. ASP.NET hands control of the web page to IISInterface
6. IISInterface looks for test.asp c:\inetpub\wwwroot\test.asp
7. IISInterface looks for test.asp c:\inetpub\wwwroot\bin\test.asp.dll, this is the compiled version of test.asp
8. If test.asp.dll does not exist or it is older than test.asp, test.asp is recompiled to produce a new test.asp.dll
9. If compilation is a success or not required c:\inetpub\wwwroot\bin\test.asp.dll is loaded and run to produce the web page
10. If the compilation is not a success a compilation report is sent to the browser.
Click to read this topic
3/28/2007 12:42:22 AM - gotham@silverfrost.com
Click to read this topic
3/6/2007 2:19:57 PM - anonymous
Click to read this topic
3/6/2007 2:10:53 PM - anonymous
Click to read this topic
3/6/2007 2:10:53 PM - anonymous
Click to read this topic
3/6/2007 2:10:53 PM - anonymous
Click to read this topic
3/6/2007 2:10:53 PM - anonymous
Click to read this topic
3/6/2007 2:10:53 PM - anonymous