Home > Archive > Visual Studio > February 2005 > Remote Debugging in VS.NET 2003 - It's Crazy (!)
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Remote Debugging in VS.NET 2003 - It's Crazy (!)
|
|
| INGSOC 2005-02-08, 9:01 am |
|
I spent a few hours today setting up remote debugging in VS.2003
I had to disable the firewall, subvert the security scheme and let anonymous
users have full access to my COM+ objects on my Windows XP workstation, but
other than that, it was smooth sailing.
And, oh yeah. I also have to run remote desktop sharing terminal between
my XP workstation and the W2K target or I can't RPC to the destination
machine.
Is that sane?
Am I normal?
Or is it just standard practice to do that?
--
Texeme
http://texeme.com
| |
| Cowboy (Gregory A. Beamer) - MVP 2005-02-08, 8:59 pm |
| Remote debugging is not a recommended scenario, so it is crazy to set up. In
most scenarios, the source repository (SourceSafe or other) controls the
files, so the user actually edit and debug locally. There are no major hoops
for local debugging.
If you think .NET is nuts, you should go back to Visual InterDev.
---
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
***************************
Think Outside the Box!
***************************
"INGSOC" wrote:
>
> I spent a few hours today setting up remote debugging in VS.2003
>
> I had to disable the firewall, subvert the security scheme and let anonymous
> users have full access to my COM+ objects on my Windows XP workstation, but
> other than that, it was smooth sailing.
>
> And, oh yeah. I also have to run remote desktop sharing terminal between
> my XP workstation and the W2K target or I can't RPC to the destination
> machine.
>
> Is that sane?
>
> Am I normal?
>
> Or is it just standard practice to do that?
>
> --
> Texeme
> http://texeme.com
>
>
| |
| Ricola ! 2005-02-08, 8:59 pm |
| Cowboy (Gregory A. Beamer) - MVP wrote:
> Remote debugging is not a recommended scenario, so it is crazy to set up. In
> most scenarios, the source repository (SourceSafe or other) controls the
> files, so the user actually edit and debug locally. There are no major hoops
> for local debugging.
So, are you recommending installing Visual Studio on my target machine ?
[color=darkred]
>
> If you think .NET is nuts, you should go back to Visual InterDev.
>
>
> ---
>
> Gregory A. Beamer
> MVP; MCP: +I, SE, SD, DBA
>
> ***************************
> Think Outside the Box!
> ***************************
>
> "INGSOC" wrote:
>
>
--
Texeme Textcasting Technology
http://texeme.com
Indie Pop Rocks @ SomaFM
http://somafm.com/
| |
| Ricola ! 2005-02-08, 8:59 pm |
|
Ok, I got it working now.
I had to set up my supporting DLLS to use "remote debugging" and specify
the remote server on which they were located in the property configuration.
Then, I also deleted an entry in the GAC for those DLLS ( which I had
put in there yesterday for no good reason ).
Now my remote service is hitting break points /and/ hitting break points
in the supporting dlls (!)
Ricola ! wrote:
> Cowboy (Gregory A. Beamer) - MVP wrote:
>
>
>
> So, are you recommending installing Visual Studio on my target machine ?
>
>
>
>
--
Texeme Textcasting Technology
http://texeme.com
Indie Pop Rocks @ SomaFM
http://somafm.com/
|
|
|
|
|