I have a Windows 7 64 Bit machine with Visual Studio 2010 Pro. On this machine, I have a Vista Business 32 bit Virtual Machine (VMWare). Now I want to establish remote debugging.
I can establish a connection and attach to an existing process (for example firefox).
But when I try to start my very simple project , I get the error "The visual studio remote debugger does not support this edition of windows".
I switched off authentification of the remote debugger.
Any ideas?
Related
When trying to install the Remote Tools for Visual Studio on my Windows Tablet , I am facing issues as the setup gets stuck on 'Initializing' and does not move ahead. I am trying to install on a Windows Tablet which is running 32 bit Operating System and 2 GB ram.
I am developing a little WPF app printing out labels.
I am using Dymo LabelWriter 400. It's connected to my computer by USB.
http://global.dymo.com/ieIE/Products/LabelWriter_400.html
I am printing out labels, but I only get half of the label out. It's a very clean cut half.
Exactly the same problem as here:
http://www.justanswer.com/printers/6bpe9-label-writer-400-turbo-printing-half-label.html
I have installed what I understand as the appropriate driver for this printer:
"NEW DYMO Label Software Application Version 8.5 for Windows XP, Windows Vista, Windows 7 and Windows 8 ONLY"
https://dymo.custhelp.com/app/answers/detail/a_id/101/~/dymo-drivers-and-downloads
I have two development environments, one live on a virtual machine. It's VMware Workstation.
The other development environment lives just on my host machine.
On the virtual machine I am using Visual Studio 2010 Professional IDE. And I am using Windows 7 professional in English.
On my host machine I am using Visual Studio 2012 Professional IDE, and I am using Windows 7 professional with Danish language settings.
The funny thing is that when I run my app in the Visual Studio 2010 IDE on the Virtual Machine the labels print out totally OK. I can see that the printer name here is: "DYMO LabelWriter 400#:7"
But when I run the same app in the Visual Studio 2012 IDE on my host machine, I only get half the label. I can see that the printer name here is "DYMO LabelWriter 400"
Any idea why I can't print out correct labels in the Visual Studio 2012 environment?
Where as I have no problems printing out from the same app in the Visual Studio 2010 environment on the virtual machine?
Perhaps I should ask this question somewhere else?
I found the solution to my problem.
I am slightly embarassed by the solution.
The solution was to adjust the size of the label template, which was done in "Advanced" under printer settings. After having done that I could enjoy my labels printed out in full size :) I never found out why there was a difference in the printer settings from the host machine to the virtual machine. I thought the settings would be the same. But never mind, now it works.
I have Visual Studio 2010 in a Vista host and I'm trying to debug a C program in a Windows 2000 guest. Apparently there is no normal way to do that because VS2010 no longer supports Windows 2000 CRT. So what I've done is I'm using the msvsmon from VS2008 instead:
C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\Remote Debugger\x86\msvsmon.exe
I have set the right firewall settings I think. I can connect to the guest machine on the host by doing \192.168.114.128\c$ for example with no problem.
When I click the VMWare play button in visual studio to debug msvsmon will start in Windows 2000 but that's it. There is a series of dings and then a message box. I am not logged in as the same user name on the host as I am as the guest. Is that really necessary? Does anyone have experience in this area or good diagnostics?
There is an option in the guest msvsmon where I can disable authentication but I still can't execute using the play button.
Thanks
Have you tried to use no authentication and then use the attach to process option in Visual Studio? You need to start the app in the Windows 2000 box first.
I'm running on a VM with Windows 7 64 bit and an installation of Visual Studio 2010. The debugger won't attach manually either. I assume there is an issue with the 64 bit machine running VS as 32 and the installation of debugger. Anyone find a good resolution?
Could this be a permissions problem? Have you tried running VS 2010 as Administrator?
I am a developer and have a XP laptop that I use to dev a SQL 2005 database and MSAccess 2003 frontend database as well as VS2003 website.
I want to upgrade to Win 7 using XP mode to install the software above. This is because I still want to install Office 2007 on Win7 etc.
Do you think XP mode on Win7 will be reliable enough for this? Also do all xp mode apps have to run in the xp mode window? Is it possible to access xp mode SQL db from Windows 7 mode?
Visual Studio .NET 2003 is not compatible with Windows 7 and would have to be run in XP Mode. Visual Studio 2005 will require Service Pack 1 to work properly as well. SQL Server 2005 will install without a problem at all.
The XP mode offered in Windows 7 is basically an integrated Windows Virtual PC. The XP mode can be reliable (if you think we can call XP reliable) but the performance of a virtual machine will always be lower comparing to a natively installed windows xp.
You can make the SQL db in the XP mode accessible from Windows 7, since XP Mode is essentially a virtual machine, you need to configure the database in the Virtual Machine to allow external connections to it as a database server.