Debugging in InterDev
Debugging in InterDev
(OP)
I'm working on a project with both Client and Server code that I want to debug. I have IIS set to debug both, yet I can only seem to debug Client code. Right now I really, really need to debug server-side code. Please help. All this is in visual studio 6 on Windows 2000 Pro.
RE: Debugging in InterDev
-----------------------------------------------------------------------------------------------------
"If you can't explain something to a six-year-old, you really don't understand it yourself."
-- Albert Einstein
RE: Debugging in InterDev
http://bellsouthpwp.net/n/o/novasoy/
RE: Debugging in InterDev
http://msdn.microsoft.com/library/default.asp?url=/libr...
I will add that I have a similar setup. I do development on my local machine, which includes testing and debugging, and then move everything over to a QA server to ensure that everything will work in that environment for a subsequent move to production. If this is similar to your situation, can you not do testing and debugging on your development system (so you needn't worry about remote debugging)? (If you try to do debugging on a remote server, then it doesn't matter what your local IIS configuration is, you have to make sure the remote server is configured correctly, and my experience has been that most server admins don't like to allow debugging on their servers.) Hope this helps. If not, post back with more info and we'll see what we can do from there.
-----------------------------------------------------------------------------------------------------
"If you can't explain something to a six-year-old, you really don't understand it yourself."
-- Albert Einstein
RE: Debugging in InterDev
BTW, I should add that InterDev is debugging my client code perfectly. It's the server-side code I need to debug and that's what isn't working. Breakpoints in the server code aren't even being triggered.
http://bellsouthpwp.net/n/o/novasoy/
RE: Debugging in InterDev
The link that I posted above also contains information that will help to ensure that you have your environment setup correctly to do debugging on your local machine. You might peruse through those section(s) just to ensure that everything is how it should be. Incidentally, when I was having problems with my setup in the past, my problem was the exact opposite of yours. I could debug the server-side code, it was the client-side that always gave me fits... Go figure...
There used to be a post here that I could reference, but it appears to be gone now... I'll see if I can find my hard copy and post some of the suggestions that were there... I do remember that it had something to do with checking all of the various pieces of configuration because that is usually where the error lies... I'll let you know if I find it.
-----------------------------------------------------------------------------------------------------
"If you can't explain something to a six-year-old, you really don't understand it yourself."
-- Albert Einstein
RE: Debugging in InterDev
Am I off base, or should this not be so hard?
http://bellsouthpwp.net/n/o/novasoy/
RE: Debugging in InterDev
- On the directory tab set Application Protection to High (Isolated)
- Click the Configuration button and go to the App Debugging tab. Be sure "Enable ASP Server-side debugging" and "Enable ASP Client-side debugging" are checked. Click OK and return to Directory tab.
- Click on the "Unload" button if not already greyed out, then OK.
-Then open Component Services and find the website's COM+ package that I was working on.
- Right-click and choose properties, on the identity tab, be sure Interactive User is checked, then OK.
- Right-click again and then choose Shut Down, then same and choose Start to restart it.
This (I believe) was what got me up and working. Something else to bear in mind - when you're in Interdev and you click on that right arrow to begin the debug process, check the processes that are being debugged (click on Debug, then Processes). In that box, you should have listed DLLHOST.exe and the IE window (presuming you are using IE) you just opened. If not, then there is a problem. Try that and let me know what you see. (Again, it shouldn't be this hard in my opinion...)
-----------------------------------------------------------------------------------------------------
"If you can't explain something to a six-year-old, you really don't understand it yourself."
-- Albert Einstein
RE: Debugging in InterDev
Frustrating.
By the way, I really appreciate you trying to help. I've been marking your posts up, but I wanted to also say thanks.
http://bellsouthpwp.net/n/o/novasoy/
RE: Debugging in InterDev
As for the error message, "Cannot attach to localhost", this sounds like it cannot even find the localhost - unfortunately, I've not run into this problem before and am at something of an immediate loss as to why this would occur. Best I can guess is that there is some other (unrelated?) problem with the IIS setup and Interdev trying to connect to it. Are you still able to open up your project like normal? Just as a guess, are you able to setup a new project (which I believe would need you to be able to connect to the localhost)? Not sure of what else it might be at the moment... Worst comes to worst, you may have to uninstall and reinstall, but I cannot help thinking there is an issue with the setup of IIS somewhere... I just had another thought, but now it's flown out of my head just as fast so I'll see if I can track it down and nail it onto a couple of slow-moving neurons...
You're more than welcome. I'm sorry that we haven't been able to track the problem down just yet. But that is what these forums are for. Goodness knows I've had lots of help from other users, so it's my turn to return the favor(s) - if I can - for others...
For now, hold off on uninstalling and reinstalling just yet. I'm just thinking that the issue lies in IIS somewhere...
-----------------------------------------------------------------------------------------------------
"If you can't explain something to a six-year-old, you really don't understand it yourself."
-- Albert Einstein
RE: Debugging in InterDev
Localhost is running. If I open a browser and navigate to http://localhost/builderbonds, the application comes up. It seems to execute correctly.
As an experiment, I created a fresh web project in InterDev. I was allowed to create it and everything. I created a basic page with a simple script on it that displayed the current time. I started it. It said the server was not set up for debugging, and did I want to set it up to debug. I said yes, and then it gave me that same annoying message and would not run in the debugger. I did nothing in IIS to create or alter the directory. This adds weight to your argument that it has to do with the way IIS is set up, I'd say.
http://bellsouthpwp.net/n/o/novasoy/
RE: Debugging in InterDev
-----------------------------------------------------------------------------------------------------
"If you can't explain something to a six-year-old, you really don't understand it yourself."
-- Albert Einstein
RE: Debugging in InterDev
http://bellsouthpwp.net/n/o/novasoy/
RE: Debugging in InterDev
-----------------------------------------------------------------------------------------------------
"If you can't explain something to a six-year-old, you really don't understand it yourself."
-- Albert Einstein
RE: Debugging in InterDev
http://bellsouthpwp.net/n/o/novasoy/
RE: Debugging in InterDev
Thread117-182022 (looks like they were having issues with debug/application failing to launch)
http://support.microsoft.com/default.aspx?scid=kb;en-us...
http://support.microsoft.com/default.aspx?scid=kb;EN-US... (This one may be of particular import since it covers some of the user permission issues if indeed the issue lies there.)
Let me know how these work out. Keeping fingers crossed...
-----------------------------------------------------------------------------------------------------
"If you can't explain something to a six-year-old, you really don't understand it yourself."
-- Albert Einstein
RE: Debugging in InterDev
Thanks Chopstik for your help. I hope the long tale of this journey helps someone else in a similar predicament.
http://bellsouthpwp.net/n/o/novasoy/
RE: Debugging in InterDev
The problem should be with the Catalog Class.
If you run dcomcnfg and don´t see the Catalog Class then your IIS server components aren´t well installed.
The simples way to solve this is to run the IIS Server Components setup. You can find it, for instance, on the second disk of Visual Studio 6.0, inside VID_SS folder.
Hope this helps