Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
When debugging asp.net code in visual studio, the flow doesn’t go to dependancy files unless you put a break point in the code being called. This is the first time I debug asp/VBScript code. It looks to me like I’ve to go through all the depencies
<!--#include virtual="path"-->
It’s kind of annoying and makes me lose focus of the big picture.
Is there anyway I can skip those files and keep the flow only on the current asp page?
Thanks for helping
The difference here is that in classic ASP, an include file isn’t a “dependency” in the traditional sense of the word. With classic ASP, all of these includes are compiled into the current “page” being requested, creating a single resource. Much as you cannot conditionally add these files in an If/Then statement, you cannot conditionally remove them.
My suggestion would be to jump between breakpoints and examine variables rather than stepping over each line.