I've read through many a posting either lamenting or suggesting a fix for InterDEV ignoring breakpoints. I had recently done some reorganization of the multiple web apps I support (different directory structure, different VSS structure, etc.) and found that InterDEV would no longer stop at the breakpoints I set in my VBscript ASP code. VB COM objects instantiated from the ASP code could be debugged, but the ASP breakpoints were ignored.
Another note in this forum got me looking at the entries in the COM+ Applications in the Component Services MMC -- something I had not done before. I found that some of my web apps had no entries, some had multiple entries, and there were entries for apps that I have not debugged in several years. I tried stopping, then disabling, and finally deleting the entries for the app that would not debug properly and, amazingly, it hit the breakpoint!
But I was somewhat shooting in the dark. Does anyone know why these entries are here? Why only certain apps and not others? Should they go away when I finish debugging? Why were there multiples?
Anyone else see this?
tr
----------------------------------------
T. Recko
Another note in this forum got me looking at the entries in the COM+ Applications in the Component Services MMC -- something I had not done before. I found that some of my web apps had no entries, some had multiple entries, and there were entries for apps that I have not debugged in several years. I tried stopping, then disabling, and finally deleting the entries for the app that would not debug properly and, amazingly, it hit the breakpoint!
But I was somewhat shooting in the dark. Does anyone know why these entries are here? Why only certain apps and not others? Should they go away when I finish debugging? Why were there multiples?
Anyone else see this?
tr
----------------------------------------
T. Recko