just starting to look at the Cordova tools for Visual studio.
Creating a blank Cordova probject, I am able to run (F5 debug), for Android and IOS (emulators), and also x86 windows, but for either Any CPU or x64 I get the following error..
The Microsoft Visual Studio Remote Debugging Monitor (MSVSMON.EXE) does not appear to be running on the remote computer.
So I have seen mentioned elsewhere that VS (32 bit) needs to run the above for 64 bit debugging. I have no problems running and debugging a classic desktop WPF.
I have tried disabling both my firewall (Zone Alarm) and any antivirus (Avast), but made no difference.
Anyone have any ideas what the problem could be here (or how to diagnose)
Thanks in advance for any help!
I have this same problem. I use the same applications as you do, Zone Alarm and Avast. If I try to debug and get that error, disabling or stopping the programs do not help. You need to close VS and restart it with the offending apps already disabled, then you'll be able to continue.
I stumbled across this question because I am looking for a way to keep from doing this.
Related
I have been facing the same issue as asked in this other post
Visual Studio 2015 Windows Phone Emulator not deploying
but the solution worked here is not working for me.
Windows 10 pro upgraded from home version
Visual Studio 2015
Apache Cordova "Sample" app.
In Emulator it is showing as "Starting
in the behind "Hyper-V" "Summary" it is visible but if double click the the Hyper-V "instance" it is not visible there but only in "Summary"
What am I missing here?
For the developer sake and investment, MS must make sure that the solutions are tested everywhere before releasing them.
This link will direct you to print screen of the error. https://prnt.sc/cykrgg
in the VS output we get the following last message.
My OS is 64 bit.
2>The build configuration was changed to x86 for x86-based emulator deployment.
could this be impact of 64 to 86 bit version difference or anything else?
I have Norton antivirus
I am getting
Hyper-v administrator pop up every time I try to run the app.
This case is resolved by Microsoft Support Team over a Ticket and Rohit, support engg from MS did really helped me a lot.
The reason why it was not coming up.....
My machine has a AdWareAntiVirus from Lavasoft by Name WebCompanion that was not allowing it work.
I removed it then it started working.
if any body have any problem with VS 2015 Emulator definitely focus on the Antivirus and include the Emulator XDE into exception list and also include in Firewall.
Thanks,
Ekambar
So many things happened that I don't know where to start. Seriously, shouldn't this be simpler?
Edit: Someone here knows how can I contact Microsoft to tell this? Or even, can someone tell them about this problem?
I have the last Windows 10 desktop and also have Windows Phone 10.0.10512.1000. I installed Visual Studio 2015 with tools for Universal Apps development (and also 8.1). I have a Lumia 730.
So I connected my phone with my USB cable. Everything fine, the phone gets recognized and I can navigate through the folders.
Then I started Visual Studio 2015 and created a blank universal app. Compiled and tried to deploy. Now this is happening to me: Visual Studio hangs for some moments. Eventually I get an error telling that the device was not found (DEP6200).
I already tried dozens of solutions:
disconnecting from wifi in my laptop and my phone
restarting the IpOverUsbSvc service
rebooting the computer and the phone
deleting the devices in the Device Manager
Registering and Unregistering the phone (it sometimes works)
All of the above with the phone screen unlocked
disabling Hyper-V
disabling firewall
Other solutions that failed miserably
I also tried to use that Windows Phone Developer Power Tools. When I try to use it, it asks me to install some "Phone Tools Update Pack", but when I try, it says that the operation didn't succeed, and also shows the NRE message string (object reference not set to an instance of an object).
I can go through the phone's folders without any problem. I tried to reinstall the drivers... i tried everything.
It's quite sad.
Do you guys can think of some more thing to check?
EDIT: I tested this app before doing all this: https://blogs.windows.com/buildingapps/2015/07/09/just-released-windows-10-application-deployment-tool/
And it worked. If that's the case, is Windows Phone 10 deployment over Visual Studio working already or we have to wait some more time?
Edit2: After making some changes to my app manifest and choosing "ARM" config, now I get this:
1>Deploying to SD Card...
1>Updating the layout...
1>Copying files: Total <1 mb to layout...
1>Checking whether required frameworks are installed...
1>Framework: Microsoft.NET.CoreRuntime.1.0/ARM, app package version 1.0.23117.0 is not currently installed.
1>Framework: Microsoft.VCLibs.140.00.Debug/ARM, app package version 14.0.23019.0 is not currently installed.
1>Installing missing frameworks...
But it just stays there. It's stuck, and it stays there forever. At least I got some info... Its more or less the same steps that WinAppDeployCmd does, but the command line app does it successfully.
Somehow the problem got solved. I created a brand new project and did this:
1 - In your phone, try disabling the developer mode on your phone. What an unexpected development!
2 - Disable the "phone discovery" thingy. I don't know the name of this configuration in english (as my phone is in Portuguese). Just in case.
3 - Choose the correct architecture. This is obvious, right? In my case, ARM. If you try deploying with x86 or x64, it should give you an error. For me, it didn't.
From now on, you should be able to deploy your apps in both developer mode and non-developer mode. It just works, somehow. And it might NOT work for you, sorry. I think I got lucky.
It worked even after a reboot. So the solution is "pretty solid" (in an universe where gelatine is pretty solid).
I had the same problem. I tried the fix of the comment and went to devices manager.
Under USB-Devices there were three Lumia 920s listed.
I selected the second one and clicked on uninstall.
At the end it asked me to restart the Computer. I clicked on NO.
(When I uninstalled the first or third one, it didn't ask me that).
Then the error disappeared (now another common one appears (HRESULT: 0x80073CF6))
I have a Lumia 950 xl, with windows 10 installed, anniversary version. I had the same problem, and my solution was to turn on 'Device discovery' and 'Device Portal', and also keep the 'Developer mode' on.
I believe the only necessary option was the 'Device discovery' though!
Just in case someone still runs into this issue, I had something very similar with my Visual Studio 2015 professional update 1 but I couldn't even deploy to an emulator.
The issue has gone after I upgraded to Visual Studio 2013 update 3.
I had the same issues on Windows 10 with Visual Studio 2015. I updated the the UWP SDK to Anniversary Edition Build 14393, set the target framework to this and it worked. I guess the incompatibility between the device version and sdk version was not allowing the device to be discovered by Visual Studio.
While running my application in debugging mood in visual studio 2013 it keeps loosing focus from my browser and the IDE. If i stop debugging then the problem doesn't occur.
I am using windows 8.1.
This is being one heck of a problem and cant find a proper solution. Would be a great help anyone can give me solution for it.
I had the same problem running windows 8.1 on a Lenovo w540. To solve this I used the code from this post. It turned out to be wermgr.exe trying to report an error in xrdd.exe which is the X-Rite Device Services Manager. This has never run correctly on my machine. I still get warnings about my monitors needing to be re-profiled for colour calibration.
Anyway I'm not sure if the problem lies with windows reporting the error or xrdd.exe itself but I have uninstalled X-Rite Device Services Manager and this has solved the problem for me.
Our Silverlight app has met one issue which can only be reproduced in one specific PC with IE9(x64)(this issue can’t be reproduced in dev machine with the same version of IE),so we need use remote debugging, however, it seems not possible because it always tell me that cannot attach to the IE process (use Visual Studio 2010).
I find that http://forums.silverlight.net/t/100057.aspx/1 tells Silvelight does not support remote debugging? Is there any update on this? Any idea to enable debugging in such scenario?
I have a VB6 app that loads initially (for a small prompt to enter a license key, only on the first time). It works fine on my machine (windows 7).
I had complaints of it crashing on someone else's machine (both xp and 7), so I made a Windows XP virtual machine. I installed it on the virtual machine, it crashed. I wanted to see where it crashed so I installed Visual Studio on the virtual machine so that I would get a debug prompt. When I ran the program again, it worked.
I am more familiar with C++ and had these kinds of problems, so I figured it was some sort of runtime issue.
I found this VB6 SP6 Redistributable Runtime:
http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=24417
I installed that, and it still wouldn't run.
Any ideas where to go from here?
Edit:
I have tried depends.exe, it only shows MSJava, which I've heard I can ignore. Does depends.exe also show things like .ocx (Active X controllers?) that are required?
Also, from the cmd prompt, %errorlevel% doesn't seem to get populated. Is that a VB6 things, or does that indicate that this is truely a crash and not a user exit?
Open the Visual Basic project and check both "References" and "Components" under the "Project" menu.
Since it is crashing with the VB runtime installed it is likely a component that you have referenced in the project that either does not exist (or is not registered) on the client under test.
This should be a simple fix.
I had the same problem on my windows 7 computer.
I have uninstalled everything, changed my windows theme to Windows Classic.
I changed following properties of VB setup file.
Right click on setup.exe and go to properties and in compatibility tab change the compatibility mode to windows XP SP2. And in settings uncheck the following check boxes.
Disable Visual themes
Disable Desktop composition
Disable display scaling on high DPI settings.
Run this program as an administrator
And have completed installation.
Followed by installing VB 6 service pack 6 from here.
http://www.microsoft.com/en-us/download/details.aspx?displaylang=en&id=24417
Hope it helps.
It may require something else other than just the runtime, have you tried viewing it with dependency walker http://www.dependencywalker.com/ on the machine that it crashes on?
It should quickly point out any missing references.
Maybe try again, create a new VM, but install the remote debugger instead of the full VS.
You should create an installer for your application. There may be more dependencies than just the VB6 runtime. A good installation tool will detect at least some of necessary dependencies for you. Have a look at this question or this question