Solved

visual studio 2003 does not step into breakpoint in .inc files

Posted on 2010-11-23
3
406 Views
Last Modified: 2012-05-10
Hi,

Unfortunately I still have one website that I have to manage in classic asp. for this reason I am using the now old visual studio 2003.

I am working on an XP SP3 machine IIS 5.1

I can debug my asp files no problem, however the debugger ignore breakpoints within .inc files.

I do not have the freedom to avoid using .inc files because the website is only managed by me; I am not the developer who originally coded it.

I have noticed that .inc is not in IIS Mappings.
0
Comment
Question by:brillox
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 15

Accepted Solution

by:
crisco96 earned 500 total points
ID: 34204816
I think you're out of luck with directly debugging include files. The way include files work is IIS just takes the code from the include file and directly injects it into the asp page so you can't really debug the include file.

A couple of options that may help you with any issues you have is you could "debug" the old fashioned way by just putting response.write in the include file to write out any variables you want to know the value of.

Additionally if you do want to debug the code in the include file you could just copy the code from the file and paste it in your asp page in place of the include directive.
0
 

Author Comment

by:brillox
ID: 34205986
Additionally if you do want to debug the code in the include file you could just copy the code from the file and paste it in your asp page in place of the include directive.

this is exactly what I am doing; I just thought that maybe I missed out any conifg options on IIS..  luckily for me this is the ONLY ASP webiste I have to manage :-)

well.. you are the lucky one that get's easy points.. :-)
0
 

Author Closing Comment

by:brillox
ID: 34205998
Thanks for answering
0

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

I recently decide that I needed a way to make my pages scream on the net.   While searching around how I can accomplish this I stumbled across a great article that stated "minimize the server requests." I got to thinking, hey, I use more than one…
Hello, all! I just recently started using Microsoft's IIS 7.5 within Windows 7, as I just downloaded and installed the 90 day trial of Windows 7. (Got to love Microsoft for allowing 90 days) The main reason for downloading and testing Windows 7 is t…
Nobody understands Phishing better than an anti-spam company. That’s why we are providing Phishing Awareness Training to our customers. According to a report by Verizon, only 3% of targeted users report malicious emails to management. With compan…

736 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question