Remote debugging to system with .Net 2.0 framework
- From: Ken Allen <kendrhyd@xxxxxxxxxxxx>
- Date: Fri, 24 Feb 2006 11:42:34 -0500
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
.
- Prev by Date: "What's This" implementation via menu
- Next by Date: Re: 17 Minutes With Bill Gates
- Previous by thread: "What's This" implementation via menu
- Next by thread: Problem with abstract classes
- Index(es):
Relevant Pages
|
