I need to work on an out-of-browser Silverlight application, provided as a VS 2010 project.
I am on a Windows 10, 64-bit machine, with a Silverlight 5 installation. I have successfully installed Visual Studio 2010 SP1, 32-bit, on this computer and been running SL out-of-browser projects with it. Now, I want to execute the project in debug mode from VS 2010 (launch from green arrow), but I get a textbox error message saying that the 32-bit version of the Visual Studio Remote Debugging Monitor (MSVSMON.EXE) cannot be used to debug 64-bit processes or 64-bit dumps.
Since I have installed on my Windows 10 computer several VS versions, including the 2017 one, I tried to "fool" the VS 2010 debugger by copying in the right folder debug correspondents from the 2017 folder, both 32 and 64 bit; but that didn't work.
I have also asked a question on the MSDN VS Forum, in the "Debug" section, but got no answer.
Please note that the build executes OK, that I can install the binary output as an SL application and that it runs perfectly.
My question is: how can I make working the debug mode for my Silverlight application in VS 2010 SP under these circumstances?
I installed VS2010(also installed the SP1 for it) in my windows 10, to create the SL5 app, I install the SL 5 SDK, and then test it like the video:
https://channel9.msdn.com/Blogs/MSDNSweden/Debugging-Silverlight-4-Out-Of-Browser-applications-in-Visual-Studio-2010
I use the same steps for the Silverlight 5 app in my side, it works well.
Could you debug or run your app before using your VS2010 in your windows 10? Not run the SL 5 app, how about a simple SL 4 app? Please also deactivated the firewall and antivirus in your windows. View the result again.
Related
I'm facing the following issue:
Background
I have a Win32 legacy application (exe & dll's) and drivers (dll's) written on Visual Studio 6.0 that used to run
well in Debug version on Windows Xp (Please Note: We need it in DEBUG configuration & not Release).
I copy the Visual studio 6.0's msvc* type dll's, MFC dll's & manifest files along with the exe to make it run.
Issue:
The same legacy 32-bit application & driver dll's have now been newly compiled in Visual Studio 2008 DEBUG mode.
It is then copied to a PC running on 64-bit Windows 10 PC (also tried Windows 7 without success) without having VS2008
installed. I copy the VS2008's msvc* type dll's (msvcp90d.dll, msvcr90d.dll), MFC dll's and manifest file (Microsoft.VC90.DebugCRT.manifest) also along with the exe.
On launching this debug version of the application (it does many initialization activities on startup and also calls the init methods of driver dll's) it crashes on starting up both on a 64-bit Windows 10 & Windows 7 PC.
What works:
When VS2008 is installed on the Windows 10 PC, the application's debug version launches correctly without crash and works fine.
(Also please note that same application's Debug build using the old Visual Studio 6.0 works fine on Windows 10).
What DOESN'T work:
When VS2008 is NOT installed on a Windows 10 PC, the application's debug version crashes while it is being launched.
Requirement
We absolutely need the DEBUG configuration of the application to run on the Windows 10 PC.
Development environment
OS for development: 64-bit Windows 7
Target OS: 64-bit Windows 10
IDE: Visual Studio 2008 SP1
Application & driver dlls/exe's: 32-bit
I have tried many workarounds like building by using 32-bit paths in VS2008 ($\Program Files (x86)\Microsoft SDKs\Windows..),
installed redistributables of VS2008 (both x86 & x64),
running as 'Administrator' user,
running in compatibility mode (Win Xp..),
copying dll's from system32 folder of a PC having VS2008 installed to a PC without VS2008 etc.. but the Debug build always crashes on it's startup.
Any help or pointers would be appreciated.
Please let me know if you would like to have further details.
Thank you in advance.
Last night, I downloaded Unity to start developing games with my brother. The installer also gave me Visual Studio 2015 and MonoDevelop, which I gather is basically a slightly modified Visual Studio.
This morning I discovered the problem: MonoDevelop will open, but Visual Studio won't. It always came up with a pop-up box saying "The program can't start because api-ms-win-crt-runtime-l1-1-0.dll is missing from your computer."
According to this other StackOverflow question, I need to download the Visual C++ Redistributable for Visual Studio 2015. But before doing that, I decided to check if I already had it, just in case.
I opened "Programs and Features" and beheld that I already had nine other Visual C++ Redistributables installed on my machine. This image shows the list.
Included are the 2010, 2012, 2013, and 2015 redistributables for both x86 and x64. I don't know if this is typical or not but it certainly seems excessive.
Despite all these, my Visual Studio still won't open. Do I need to install another one? I'm happy to do that if I need to; I just want to start coding.
(I also had this same problem with Microsoft Office 365 before I just gave up and downloaded Microsoft Office 2013 instead, which works fine. Perhaps it's a problem with my machine? I'm running Windows 7 64 bit, for what it's worth.)
You also need to install the Universal C Runtime
The Windows Update package on this page allows Windows desktop
applications that depend on the Windows 10 Universal CRT release to
run on Windows Vista SP2, Windows 7 SP1, Windows 8, and Windows 8.1
S14.
Extract the WindowsUCRT.zip and install the Windows6.1-KB3118401-x64.msu (note if you get a hang at "Searching for updates on this computer", cancel the install, stop the WU service and try again to install the update).
Unable to attach debugger "File not Found" using template for Apache Cordova in vs 2013. Happening on both Win 8.1 64 machine and win 7 SP1 64 machine.
Project builds and runs correctly in both emulator and ripple but generates error "Unable To Attach. The system can not find the file specified." No further information is given - as in what file is not being found, which would have been nice.
Unlike the other solutions I have seen on web, installs on both machines ARE on a system drive. Latest updates are installed for node, git and android sdk. Environment variables and path variables are correct on both machines. Tried all api's 19 and above, uninstalling and reinstalling the tool multiple times, updating from command line.
Issue occurred after switching from visual studio 2013 Pro update 3 to community edition update 4 on both machines.
Have even tried uninstalling every piece of software having to do with android dev (Eclipse, Android Studio, Cordova, Phonegap, the tool) and reinstalling the Cordova Tool with all of the default options. Still same error on both machines - currently just using chrome to debug.
Noticed that it seems to be a similar error(the adb.exe error) but without the file name, given when trying to debug on a phone that has less than 4.4.
Any suggestions? Thank you for any help in advance.
I had exactly the same error and I successfully resolved it.
My configuration:
Windows 7 Pro 64 bits - French
Visual Studio 2013 Update 4 (French Edition)
CTP 3
What I did to solve the problem:
First, I installed ENU Language Pack for Visual Studio to install English language
Then, I switched the language of my Visual Studio to english
Finally, I repaired my CTP 3.0 installation.
After that, I was able to debug application from my android device.
Another solution (but not suitable for everyone since it's required a MSDN Account) : using the Visual Studio 2015 Preview.
What is the version/build number/size of the resources assembly in
C:\Windows\Microsoft.NET\assembly\GAC_MSIL\Microsoft.VisualStudio.WebClient.Diagnostics.HtmlToolHost.resources\12.0.* ?
You can right click on the binary and check its properties.
Thanks
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.
Can I use Visual Studio 2011 running on the Windows 8 Developer Preview to publish programs that will not only run on Windows 8, but that will run on Windows XP, Vista, 7 and 8? I know that using Visual Studio 2010 while Running XP can produce applications that will run on XP and up, but can it work the other way?
UPDATE: By Publish I mean that I want to package my application into an installer and distribute it.
I am Using Visual Basic .NET as the programing language within Visual Studio 2011
UPDATE 2: Also, If I can't make my app available on XP through 8, then can I use Visual Studio 2010 to do this or is it a matter of Operating Systems?
The version of VS11 that comes in the Win8 DP will only let you build Win8 apps. You can install VS2010 side by side with it though to do other types of development.