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.
Related
When you hit the run button in Visual Studio for Mac, what service is it that actually temporarily runs the website? So for example if I ran the application in Windows the site would be running under Local IIS (assuming I had nothing else configured) - is there a Local IIS equivalent for Visual Studio for Mac?
I'm running into issues trying to register Visual Studio 2017 and 2015 with my Visual Studio Online Subscription (a.k.a. MSDN). I'm using a VMWare VDI using their Horizon Client if that matters. The OS is Windows 10, and the Visual Studio SKU is Professional. My client requires me to run under two separate identities, one with limited privileges for non-development work, and an administrator account for development work (annoying, but not unreasonable given my client is a very large corporation). So, I run Visual Studio under that admin account using Run as administrator.
My problem: On the virtual machine Visual Studio hangs when I click the Sign-In button, or the Check for an updated license on the product registration sign-in page. Note: This problem only occurs from the virtual machine using my administrator account. It works fine on the virtual machine under my normal non-admin account. Nor do I have issues on the physical machine I'm using to run the VM. That said, my client requires me to use the virtual machine.
I'm just wondering if anyone else as seen this same issue. There is something about running under my admin account on VMWare that is hanging Visual Studio registration as soon as I click sign-in. Likely a firewall or proxy setting, not sure. I'm working closely with my client's IT Operations, but they are as perplexed as I.
I develop Windows 8.1 Store apps using VisualStudio 2013 preview. Hence i have to test my app in the Windows Surface 8.1 (ARM) device to debug. For the remote debugging i installed the VisualStudio 2013 Remote tools for ARM device.
When I try to run the Remote tools exe. I get App cant run in this PC issue in my Windows 8.1 Surface RT. Could you please help me in this ?
My guess is that you are trying to run the x86/x64 remote debug tools on the ARM tablet because there is no VS2013 remote debugger for ARM.
I also encountered the same issue - this is what i did: I installed the Visual Studio Remote Debugging Tools 2013 (if you have installed already, uninstall it, and also uninstall the one for 2012 too).
After installing it, go to this path in your Surface:
C:\Program Files\Microsoft Visual Studio 12.0\Common7\IDE\Remote Debugger\arm
Inside there should be an executable named msvsmon.exe; run it.
When you start the remote debugger for the first time, the dialog is called Remote Debugging Configuration, so just click on "Configure Remote Debugging" button at the bottom.
Pin the msvsmon.exe to the start screen by right-clicking (or using touch, touch and hold until the menu options appear).
This works for me and now im able to deploy into my Surface RT under Windows 8.1, from VS 2013.
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 am using VS 2010 and trying to remote debug a Window 8 machine. I can't find a VS 2010 remote debugger stub compatible with Window 8. Is it possible to remote debug Window 8 with VS 2010 or must I upgrade to VS 2012?
Windows 8 applications can only be created/debugged with Visual Studio 2012 or newer.
John Wiese
Microsoft - Sr. Technical Evangelist
jwiese#microsoft.com
#johnwiese
Actually it is possible.
Install Microsoft Visual Studio 2010 Remote Debugger Tools on the Windows 8 client
https://www.microsoft.com/en-au/download/details.aspx?id=475
Each time you open msvsmon.exe, it tries to use Windows Authentication. You need to disable this when opening, with this command;
msvsmon.exe /noauth /nosecuritywarn
It's related to this issue;
Remote debugging in visual studio: remote debugger does not support this edition of windows
Here's a screenshot