How to debug classic ASP in VS?

 
I have been trying for a long time now to set up a good debugging environment for my company's website, which, unfortunately, happens to be in classic ASP. Up until now I have never had a way to step-through breakpoints and have, instead, coded a lot of "response.write", but I'm increasingly coming up to coding errors that the response.write's never help on, so I REALLY need to use Visual Studio to help out.
I currently have MS Visual Web Developer 2008 Express Edition and every time I try to do a Build on the website from a remote computer to the web server it brings up this error, which references a non-existent web.config file. (Is a web.config file even necessary for a classic ASP website? I never had one before):
********************

 Error 114 An error occurred loading a configuration file: Failed to start monitoring changes to 'S:\Inetpub\websites\[...]\craigslist' because the network BIOS command limit has been reached. For more information on this error, please refer to Microsoft knowledge base article 810886. Hosting on a UNC share is not supported for the Windows XP Platform. S:\Inetpub\websites\[...]\craigslist\web.config

 
********************
If, however, I try to do a Build directly from the web server itself (using the server's MS Visual Web Developer 2010 Express Edition) I receive an ENORMOUS number of similar errors such as:
********************

 Error 1 The <compilation> element of the Web.config file does not have a 'targetFramework' attribute. Therefore ASP.NET assumes that the Web application targets the .NET Framework version 3.5 or earlier, but ASP.NET could not find files that are installed with the .NET Framework version 3.5 that it needs to compile. If you are compiling this Web application for version 3.5 or earlier of the .NET Framework, make sure that version 3.5 of the .NET Framework is installed. If you are compiling this Web application for version 4 or later of the .NET Framework, add the 'targetFramework' attribute to the <compilation> element of the Web.config file (for example, '<compilation targetFramework="4.0">'). C:\Inetpub\websites\[...]\test_list.aspx 50  

********************
 
I have so many questions and am pretty confused by the process of Building and Debugging an ASP website (as opposed to a .NET website). Can someone please help, so that I can properly start debugging this site?
Thank you very much.

I'm afraid that you can't use Visual Studio to debug a Classic ASP script.  ASP uses VBScript, which is an interpreted language.  While you can use editors that will do syntax checking, the runtime errors won't be seen until the ASP script is executed.  The only real debugging tools for ASP/VBScript are response.write and the error messages return but the ASP interpreter (some of which may be obscure).
 
ASP.NET was created to fix this very limitations.  But Visual Studio can't debug a Classic ASP script because it is not compiled language.