The goals of Gotham are to:

1. Make it possible to (more) easily debug ASP code
2. Make the transition from ASP to ASP.NET easier

There is one important effect on your code that I am sure you will like:

• Gotham compiled code runs between four and six times faster

Gotham comes in two parts:

• a compiler which converts the ASP source code into .NET compiled code
• a run-time which directs .asp page requests to the correct .NET compiled code and supports the ASP environment

When developing using Gotham there are three primary ways you can operate:

1. You can compile your source files using the command-line compiler. The compiler diagnostics are presented at the command prompt that you type into. You then run the code by making a page request via IIS
2. You can compile your source file using the command-line compiler into an executable. You then run the executable and the output is sent to the console. This is not available to ‘normal’ ASP developers and can be very useful when developing code that is not dependent on the HTML output.
3. You can work in fully-automatic mode where as you make source changes the Gotham run-time spots the updated source and demand compiles your code. Compile time errors are delivered as a web page directly into your browser. At present Gotham only detects source updates at the page level -- so changes to include files will not cause a recompile – you will need to use the command line compiler in these cases.