Well, that's been one of the inherent problems with Classic ASP development
all along. There really hasn't been a great product to do server-side
debugging.
You man not like this answer, but I always coded in good old "Visual"
Notepad (a.k.a. Notepad). There is no debugging at all really, just the
scripting errors that come back from IIS to the browser.
This was one of the many reasons why MS came up with a whole new Visual
Studio. Debugging .NET applications (ASP.NET) is much more reliable and
robust.
"Wanjun Yu" <wa*******@hotmail.com> wrote in message
news:OC**************@tk2msftngp13.phx.gbl...
Scott,
Since Visual InterDev is buggy, what would you recommned to use for
debugging ASP?
Thanks!
Wanjun
"Scott M." <s-***@badspamsnet.net> wrote in message
news:%2****************@TK2MSFTNGP12.phx.gbl... You are asking about Visual InterDev? This is the MS ASP.NET newsgroup.
You do need FrontPage Server Extensions installed on IIS for Visual
InterDev to function correctly.
Debugging your Classic ASP pages with InterDev was always buggy at best.
The server extensions are probably not to blame.
"Wanjun Yu" <wa*******@hotmail.com> wrote in message
news:Os****************@TK2MSFTNGP09.phx.gbl... Is FrontPage Server required for using InterDev?
I am a beginner. When I tried to create a project, the wizard showed
that MS FrontPage Server Extentions have to be running on the server. I was
having trouble to debug the other ASP pages, I wonder if this was causing it.
Thanks!
Wanjun
