Scott, I could finally enable the "Start Debugging" button on the
toolbar & under the "Debug" menu!
All I did was clicked "File"--->"Recent Projects" from the menubar (I
save all my ASPX files in the C:\Inetpub\wwwroot\ASPX directory). It
listed just 1 project i.e.
http://localhost/ASPX. I just clicked on it.
2 ASPX files existing in the above-mentioned directory opened & to my
surprise, the "Start Debugging" button & menu got enabled. Now by
pressing F5, I am now able to step over each line in the code. Finally
good riddance to bad rubbish
I guess the reason why I couldn't debug earlier was because I was
opening ASPX files as single independent files & not as part of a
project which is why the "Start Debugging" button & menu were disabled.
Could that be the cause why VWD wasn't allowing me to debug ASPX pages?
Well, now that I am able to debug, I came across another petty problem
- not a problem - rather a nuisance. Suppose I am working with an ASPX
file named "Hello.aspx" & that's the only file open in VWD currently.
Now when I click the "Start Debugging" button (note that only 1 ASPX
file is open presently), irrespective of the ASPX file I am currently
working on has errors or not, all the ASPX pages residing in the
above-mentioned directory get debugged. As a result, errors existing in
other ASPX pages, though they aren't open in VWD, get clustered in the
Output window & in the Error List window. How do I avoid this so that
VWD debugs only that ASPX page which I am currently working on?
Arpan