![]() The network type of the guest is bridged (it is). Computer name of the guest is unique on the network (it is)ĥ. Remote debug monitor matching the name specified in the config appears (it did)Ĥ. (OK, I did 2 out of the three - I don't think the domain is the issue, but I can't join the guest to our domain without being shot at dawn).ģ. Logon to the VM with the same user/password/domain. However, if I instead select "start debugging in a virtual machine", I see msvsmon.exe start in the host system with title and it has 5 entries that say "computername\cumming connected" that beep before Visual Studio pops up a message box saying "The visual studio debugger failed to start the debugging session in the virtual machine". If I invoke "start without debugging in a virtual machine" from within Studio, my application starts just fine in the VM. I have disabled the firewall within that VM, and I have created and logged into the VM as a user account that has the same user name and password as the account I'm logged into my host system, although the host machine belongs to a domain and the guest is a member of a workgroup with the same name as the domain. Within Studio I set the configuration to point to a VM that I have already created. I am running the latest build of VM Workstation 6.0.2 build 59824, and I installed the plug-in for Visual Studio 2005.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |