467,170 Members | 1,061 Online
Bytes | Developer Community
Ask Question

Home New Posts Topics Members FAQ

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

Remote debugging to system with .Net 2.0 framework

I have encountered a problem with remote debugging under VS 2005 and
..Net 2.0 -- it seems that the framework installation does not include
the "Microsoft .Net Framework 2.0 Configuration" tool!

My preferred method of debugging uses these steps:

1. Share the directory that contains the debug image; also share the
folder that contains the debug monitor.
2. Configure the project debug mode to launch the exeecutable from the
share rather than the project.
3. Indicate the specific remote system to use.
4. On the remote system, alter the zone security to permit full trust to
the local intranet.
5. On the remote system (actual not so remote as it is typically on the
same desk), start the MSVMON utility via the share to my development system.
6. Launch my application -- see the console or GUI interface on the test
(remote) system and the debugger on my desktop.

With the standard installation of the .Net Framework 2.0, however, I
cannot edit the zone security, and therefore cannot use remote debugging
in this manner.

a. How can I edit the zone security without installing Visual Studio
2005 on all of the test systems?

b. Is there another debugging model that does not require me to copy
executable images between systems (which almost always indicates the
remote version does not match the local debug information and the
debugger seldom displays the proper lines).

-ken
Feb 24 '06 #1
  • viewed: 2774
Share:
1 Reply
DWS
I think you need to install the remote tools.

"Ken Allen" wrote:
I have encountered a problem with remote debugging under VS 2005 and
..Net 2.0 -- it seems that the framework installation does not include
the "Microsoft .Net Framework 2.0 Configuration" tool!

My preferred method of debugging uses these steps:

1. Share the directory that contains the debug image; also share the
folder that contains the debug monitor.
2. Configure the project debug mode to launch the exeecutable from the
share rather than the project.
3. Indicate the specific remote system to use.
4. On the remote system, alter the zone security to permit full trust to
the local intranet.
5. On the remote system (actual not so remote as it is typically on the
same desk), start the MSVMON utility via the share to my development system.
6. Launch my application -- see the console or GUI interface on the test
(remote) system and the debugger on my desktop.

With the standard installation of the .Net Framework 2.0, however, I
cannot edit the zone security, and therefore cannot use remote debugging
in this manner.

a. How can I edit the zone security without installing Visual Studio
2005 on all of the test systems?

b. Is there another debugging model that does not require me to copy
executable images between systems (which almost always indicates the
remote version does not match the local debug information and the
debugger seldom displays the proper lines).

-ken

Mar 2 '06 #2

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

3 posts views Thread by Nick Bunton | last post: by
7 posts views Thread by Mikael Östberg | last post: by
2 posts views Thread by Ken Allen | last post: by
3 posts views Thread by Steve Wark | last post: by
reply views Thread by Ken Allen | last post: by
reply views Thread by Benny | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.