Debugging in multiple domains
From: LittleRicky (anonymous_at_discussions.microsoft.com)
Date: 03/04/04
- Next message: Suresh: "RE: OleDbParameter Query: Multiple parameters"
- Previous message: John Holmes: "Problems with Validator controls"
- Next in thread: Alvin Bruney [MVP]: "Re: Debugging in multiple domains"
- Reply: Alvin Bruney [MVP]: "Re: Debugging in multiple domains"
- Reply: Alvin Bruney [MVP]: "Re: Debugging in multiple domains"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 4 Mar 2004 15:11:06 -0800
Has anybody succedded in running Remote Debugging when your web client is in a different doman than your web server?
I've done everything I can think of to get this to work. I can access code from Visual Studio, run builds, do "start without debugging" or run straight from my browser, no prob. But as soon as I start up the same code for debugging I get "Unable to start debugging on the Web Server" - and something about not resolving the URL for the start page.
I've read all the MSDN stuff I can find - checked all the stuff they talk about - DCOM config, permissions, setting the browser to trust the web server IP - no dice.
I can always copy code back to my client box - and run it on my local IIS - but things are just totally pig-slow when I'm running IIS, V Studio, and ASPNET processes all on the same machine...just not worth it. I really want to debug.
And hey, this wasn't my idea...I think trying to develop accross domains is inherently insane - but I'd really like to get my debugger going - I haven't seen any articles that say it can't work.
Any ideas?
- Next message: Suresh: "RE: OleDbParameter Query: Multiple parameters"
- Previous message: John Holmes: "Problems with Validator controls"
- Next in thread: Alvin Bruney [MVP]: "Re: Debugging in multiple domains"
- Reply: Alvin Bruney [MVP]: "Re: Debugging in multiple domains"
- Reply: Alvin Bruney [MVP]: "Re: Debugging in multiple domains"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|