When I debug and step any windows phone app on my virtual machine I get the "No Source Available", "The current thread is not currently running code or the call stack could not be obtained".
This is regardless if I debug on the device or the emulator.
It seems like it breaks on the correct breakpoints thou, and continuing works fine.
Stepping through server code works fine.
The virtual machine is just set up for this and only contains Windows 8 (updated), Visual Studio 2012 Pro (complete, updated), Google Chrome, Start8 and Windows Phone SDK 8.0.
Repairing the Visual Studio installation solved the problem.
Related
I am building an app on Xamarin Forms Framework and my app crashes when installing on a physical android device.
It gets fixed when I clear storage and run it again, then my app wont crash and runs good,
But every time i reinstall my app it first crashes.
Another weird thing is Release Built and Debug Built run well on the visual studio debugger.
I am working on trying to fix it all day but no success tried to cancel Optimize my Code, tried to disable link but nothing.
Edit: I use a Mac so I tried to move my project to my Windows PC and released the app to my physical device and it works well, maybe its a Visual Studio Mac Bug?
I'm experimenting the following error when I run the Windows App Certification Kit on a brain new C# Universal App: "Task failed to enable HighVersionLie".
Windows 10 1709 (Build 16299.125)
Visual Studio Pro 2017 (15.5.4)
New project C# Universal App (no additional code added to the project)
Min SDK version: Windows 10 (10.0; Build 10240)
Target SDK version: Windows 10 Fall Creators Update (10.0; Build 16299)
Windows App Certification Kit: 10.0.16299.15
If I generate the appxbundle, the certification kit fails with error "Task failed to enable HighVersionLie".
If I copy this appxbundle on another Windows 10 instance with the same certification kit and pass the test again, there is no error (the HighVersionLie passed successfully)
The "HighVersionLie" test checks to see if your app will crash if it is told that it is running on a new, higher version of Windows (a version which has not been released yet).
I'm guessing that the machine you are seeing the problem on has a problem running this test, and it is not the app's problem.
If you run Visual Studio as Administrator, and then run the tests, do you still see the problem?
You might also check for a corrupt installation by running sfc /scannow from a command prompt, or reinstalling Visual Studio
Finally, you might try running Event Viewer, and checking the "Application" log to see if there are any Errors around the time you ran your certification test. If you see an error here, Google the description to find out what's wrong.
If you still think it is a problem with the app, you might check out my HighVersionLie answer here.
I'm trying to debug my C#-mono program on a Pi 3 using the latest MonoRemoteDebugger (1.0.10).
The program compiles on both the build machine (a windows 10 64 bit laptop) as well as on the target (Pi 3). The binary also runs on the target machine.
But when i try to remote debug using Visual studio 2015 Community with the MonoRemoteDebug extention it fails.
The debug server that runs on the target machine is found by the extention client.
When i select the server and press connect then it connects.
But when it tries to start the binary it fails, it returns with the message that the .exe cannot be found.
It seems that is tries to find it in the directory of the development machine (C:\users\user\projects\project\Program.exe).
I have followed this tutorial:
https://mmkaram.wordpress.com/2015/04/18/run-and-debug-c-net-on-a-raspberry-pi/
and also read the following post Mono remote debugging from Visual Studio
But i can't seem to get it to work, can anyone help me?
I would suggest you to use Xamarin Studio.
Remote-Debugging from Windows to Linux (for me on a Beaglebone) works without any problems.
https://store.xamarin.com/account/my/subscription/downloads#all-versions
https://eladnava.com/debug-remote-mono-apps-via-xamarin-studio/
I also tried to get the debugging running from within VS. It is "possible", but only very basic and awkward to use.
Xamarin Studio is also free and fully compatible to the VS Solutions. So if you want you can use VS to write your code and then load the solution in Xamarin Studio to do your debugging.
I am running VS2015 CTP6 on a freshly installed and updated Windows 8.1 N x64 VM.
Hyper-V support is enabled, hypervisor.cpuid.v0 = "FALSE"and vhv.enable = "TRUE" are set to vmx-file.
When i try to run the build with a Visual Studio Emulator for Android-device VS will tell me "starting emulator" forever. No error, no window, nothing at all.
The included AVDs (like AVD_GalaxyNexus_ToolsForApacheCordova) start fine, just the new Microsoft VS Emulator for Android isn't working.
After canceling the building-process a message pops up: "Could not start emulated device 'VS Emulator....'" which will now always pop up instantly (after building) if i hit F5. So after canceling the build once VS won't even try to start the emulator again (on that project with that specific emulation-device).
In hyper-v-manager there are no computers at all. \Microsoft Visual Studio Emulator for Android\1.0\ does not contain a XDE.exe but 2 vsemu.vhd's.
I also followed this guide and tried to start the emulator as a standalone.
"pathto\XDE.exe" -vhd "pathto\vsemu.api19.vhd" which will actually start it up and displays "loading" on the emu screen but will crash because i haven't installed the Windows Phone support in VS.
The Visual Studio Emulator for Android can't be run nested inside another VM, particularly not a Hyper-V VM, because the emulator itself is a Hyper-V VM (and Hyper-V doesn't support nested VMs). See the last bullet in "Current limitations" at the end of this blog post.
My emulators disappeared (according to VS) after CTP6 update although all the images, SDKs etc. are still there.
I sorted it with a repair (control panel, programs, vs => modify.) It took many hours do just let it run.
Double check that the VM you are running on has enough memory(emulator will use a lot- and run Procmon to see what VS does and where it fails. Check event log and turn on logging for the VS instance you are using to look for cues.
"The Visual Studio Emulator for Android can't be run nested inside another VM"- is incorrect. My Windows10 VM is happily serving up the emulator for the different platforms and the same goes for Windows 8.1 & 8.
HyperV doesn't seem to be able to support quite yet (AFAIK) but there are other hypervisors you can use such as VMWare player- and from your config edits in the VM I assume you already knew that :)
I'll provide picture proof later (phone only right now so I'll have to edit typos as well later).
Tweaking Virtual Maschine Settings did the trick for me. I was also trying to run the Android emulator by starting a debug session in VS2015 Community for a Xamarin project. VS2015 was running inside a Windows10 VM based on VMware Workstation 12 Pro hosted by Windows7 on a i7 CPU. I ran into the following error message:
"... The Virtual Machine Management Service failed to start the virtual machine 'VS Emulator 5-inch KitKat (4.4) XXHDPI Phone.andreas' because one of the Hyper-V components is not running (Virtual machine ID ...)."
Everything worked fine after activating the following flags in the virtual machine's processor settings section:
Virtualize Intel VT-x/EPT or AMD-V/RVI
Virtualize CPU performance counters
(Preferred mode: Automatic)
Whenever i try to debug a solution for windows mobile 6 I am met with this error
The project works on other machines around the office and has worked on my machine before. My guess is a setting has changed on my machine that is causing this to fail but I haven't found any solutions.