Vmware6.5 integrated with Visual Studio

Preface: After vmware6.5 is installed, a plug-in will be added for visual studio05 and visual studio08. This plug-in often causes problems for vs, and even causes vs to fail to start or compile. In fact, many of my friends don't know what this plug-in is for, and vmware6.5 is more than N times larger than vmware5.2. Is this function useful?

Vmware6.5 plugin after installation
 

 
Why is it depressing to create a plug-in for vs? You are prompted to set the plug-in first when you run the plug-in or directly run the plug-in. You don't know what to do if you want to do it, is this function used by some programs that require multi-machine debugging?
With this question, I went to the VMware forum to check whether there are related functions.
You only need to search for VMware vitual debugger.
On this page
Http://communities.vmware.com/message/825906
I found some ideas. Based on the Forum content, I did describe the Joint Testing Process of multiple computers.

Operating principle
Like many joint testing tools, there is an end point running on different computers, with a masterProgramYou can call these clients and execute computation. This has something to do with network computing. Just like using brute force to crack a password, each computer only needs to install a client to execute computation. Use a thin client to provide services. VMware uses this principle to deploy and test different computers. VMware is the client deployed on each computer.

Disputes Caused
I believe that few people are using this function. As a result, programmers who use Vs will come up with certain methods to test distributed programs. programmers who do not use Vs will have no such problem at all, adding plug-ins has a learning process. If you do not use a plug-in, it may not be okay. As mentioned above, this plug-in often causes errors.
The method of deleting plug-ins on the internet is really cool.
The method for deleting a plug-in on the internet is as follows:
Vs2008
In the registry
Change loadbehavior under HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ visualstudio \ 9.0 \ addins \ vmdebugger. Connect to 0 (originally 3)

Vs2005 is
HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ visualstudio \ 8.0 \ addins \ vmdebugger. Connect

Source: chakman