by Rob Locher
Problem: Visual InterDev is lousy.
Workaround: Use Visual Studio .NET instead! You can create an "Empty Web Project" in either C# or VB.NET (the choice is irrelevant), and then add ASP files to it (add an "HTML Page" and then rename it to .asp). Visual Studio .NET integrates seamlessly with many source control providers such as Visual SourceSafe, which is something you couldn't do at all with Visual InterDev. You can turn on ASP debugging in the project properties dialog. You also get the Copy Project wizard which is very handy for deployment. There is one odd thing about using Visual Studio .NET to work on an ASP project, though; when you start debugging, Visual Studio will spend a split second compiling an empty DLL. Weird.
Problem: ASP assumes that your server-side code is VBScript unless you tell it otherwise somehow. This is especially a problem for include files, because you can't use a <%@ LANGUAGE="jscript" %> directive in an include file. This throws off syntax highlighting in the IDE, which is very distracting.
Workaround: If you're using Visual Studio .NET instead of Visual InterDev (highly recommended), in the Visual Studio project settings set the "client" script language to JScript. Otherwise, use <script runat="server" language="jscript"></script> blocks instead.
Workaround: use either <% %> blocks or <script runat="server"></script> blocks, but not both, so that you control the order things are parsed and not ASP. Make sure that the code to modify an object's prototype parses before the code that creates an instance of the object.