Click here to Skip to main content
15,883,705 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
See more:
Hello, I am recently in a project that is written with visual studio 6.0 sp6 but the machines involved are: Windows 10 (with the compiler) and a windows 10 where the program in question runs. However when setting up and trying to run monitor.exe and run a remote debug each F5 takes no less than 30 seconds.

I also know that it is an old tool but I have no alternatives, I have to use it. Has anyone had this problem and knows how to solve it?

Appreciate. There ... I searched for the whole site and did not find a subject that solves the issue.

What I have tried:

I already disabled the firewall, synchronized the clocks and already moved all the possible settings. Just did not move the impossible :).
Posted
Updated 11-Dec-19 7:04am
v2
Comments
CHill60 11-Dec-19 13:05pm    
If you are hitting F5 you're running the entire program, so surely this depends on what the program is doing and how it is doing it
Member 12147153 11-Dec-19 14:13pm    
Sorry I made a mistake. In this case it would be the F10 key.
CHill60 12-Dec-19 3:20am    
Have you seen the suggestions on this post … Debugging is Very Slow Via F10[^]
[no name] 11-Dec-19 14:00pm    
It takes time to "compile" and "deploy". Deploying (and debugging) on a remote machine means sending the executable and starting the debugger. If it's also compiling, it all adds up … even on a "fast" machine.
Member 12147153 11-Dec-19 14:17pm    
Ok, I get it. Let's go: The debug format executable is already on the test machine, monitor.exe is already running as well. By pressing the F10 key on the host machine communication is established and pressing the F10 key again, this in turn takes about 30 seconds the next time.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900