0

I have an ASP.NET web app with some classic ASP pages mixed in and I was hoping to step through the code for some of those pages, but when I set breakpoints in them, they never get hit; if I hover over them I see "breakpoint set but not yet bound". Is there any way to debug classic ASP pages in VS2019?

edit: A few of my aspx (ASP.NET) pages get this breakpoint error too; I'm not sure why some of the breakpoints work and others don't...

ekolis
  • 6,270
  • 12
  • 50
  • 101
  • Hmm, I tried enabling server side debugging in IIS as that link says, but now I get a different error with the breakpoints: "No symbols have been loaded for this document". Could this have something to do with the fact that my app is a hybrid of classic ASP and ASP.NET? – ekolis Aug 16 '19 at 13:35
  • The key is to make sure the debugger is attached to `Script` not compiled code. – user692942 Aug 16 '19 at 13:57
  • And now all of a sudden I can debug classic ASP code, but I can't debug ASP.NET code anymore... How can I switch back? – ekolis Aug 16 '19 at 14:24
  • 1
    When you attach to the process select both `Script` and `Managed` code types. – user692942 Aug 16 '19 at 15:50
  • OK, I tried that but I get an error saying Managed and Script can't be selected at the same time because they're not compatible... – ekolis Aug 19 '19 at 15:01
  • I guess not then, either way [asking another question](https://stackoverflow.com/q/57526327/692942) isn't going to help and just clutters the unanswered queue until someone provides [the same answer from 10 years ago](https://stackoverflow.com/a/1062919/692942). – user692942 Aug 20 '19 at 04:29

0 Answers0