469,926 Members | 1,717 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,926 developers. It's quick & easy.

Remote Debugging in VS.NET 2003 - It's Crazy (!)


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

Nov 22 '05 #1
3 1571
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

Nov 22 '05 #2
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 ?


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

--
Texeme Textcasting Technology
http://texeme.com

Indie Pop Rocks @ SomaFM
http://somafm.com/

Nov 22 '05 #3

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:
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 ?


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


--
Texeme Textcasting Technology
http://texeme.com

Indie Pop Rocks @ SomaFM
http://somafm.com/

Nov 22 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

1 post views Thread by Zanna | last post: by
reply views Thread by yurps | last post: by
reply views Thread by Ken Allen | last post: by
7 posts views Thread by | last post: by
1 post views Thread by CK | last post: by
reply views Thread by CK | last post: by
reply views Thread by Tim Bücker | last post: by
3 posts views Thread by Yves Gagnon | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.