I am facing problem in deploying windows phone 8 app in the emulator. But each time I am going to deploy its showing the message like the figure. Can any one please help me how can I get rid off this disgusting message? I am using using VS Express 2012 with update for in Windows 8.1 Pro.
You need to hit the Retry button. If that succeeds then log off of the machine and then logon again.
Pressing retry will add you to the Hyper-V administrator security group. After this you have to sign out of your development machine and then log in again for changes to take effect , and then deploy app to the Emulator.
Related
I'm currently working on Windows8.1 Phone Application Development.
Application runs fine on the emulator but when i try to deploy it on my Lumia 535, It gives this strange error message (Snapshot).
"Debug using ARM" is selected and my device is connected and unlocked.
HyperV is enabled too
thanks in advance :)
I´ve been through this hell for many hours. Tried everything. IpOverUsbSvc was up and running.
The only solution in my case was "repair" option of the visual studio installer
Try the following.. Disconnect USB
press 'Window key' + R
type 'services.msc'
press 'ok'
In the list find service Windows Phone IP over USB Transport (IpOverUsbSvc).
Right click on it
Select Restart
Connect USB and try again. (Hope your device is developer unlocked.)
I build an easy App in visual studio 2013, creating it through the windows phone project. The main thing is that it's supposed to fetch data from a API of my choice and write to an XML- document. It worked code-wise but depending on what network I was using(Wireless), It gave me either and error or it worked. It worked if I compiled with my phone as the network supplier, but not on my wireless at home or the schools network.
The error I recived everytime was "the thread has exited with code 259"
I googled for some solutions, and I guessed (Not really sure it was the answer I was looking for) that the error was due because of the phone emulator "takes" my PC's IP adress or network.
They told me to just remove my phone emulator on Hyper-V manager and then just re-start my emulation and it should work.
After this was done, all hell broke lose, cause now, visual studio can't even connect to the emulator.It creates a new phone emulator in hyper-v, but can't connect to it. When I try to compile the app I created it says "Trying to connect to "WVGA 512MB" or if I choose another "WVGA 720". It does this for about 3-5 min and then it says "An error occured. Would you like to continue?"
Now I have no idea what to do. I've googled for almost 2 days and I am at lost. I've un-installed, re-installed, repaired all my visual studio but nothing helps. I am using visual studio premium 2013 if that helps..
I guess this is due to the network issues, as you said the emulator takes the default PC's IP address. But normally after removing the emulator from the Hyper-V Manager and when you try to restart it, it should work.
If none of them works try removing all the Virtual Switches from your Virtual Switch Manager which is within the Hyper-V Manager. Then create a new Internal type of a Virtual Switch and restart your machine. Then try launching the emulator.
For more look into these:
Windows Phone 8 emulator can't connect to the internet
Windows Phone 8 emulator error - Something happened while creating a switch
(WP8) Emulator (XDE) Troubleshooting Tips
Facing a strange Problem...
In Visual Studio 2013 Ultimate my Phone App Builds correctly, i can deploy it to my device, but when deploying to the Emulator the XDE Pops up and says "Windows Phone OS is starting...".
I can see in the HyperV Manager that the OS Runs in Hyper-V, but the Emulator doesnt Show the Output and thus is no Debugging possible.
Have deinstalled VS2013 completely, restarted, new freshly installed.. no changes...
No error Messages.. nothing :(
Don't forget to install the latest quarterly updated for visual studio 2013. I ran into a problem with the emulator (VS2012) when I installed the Azure toolkit which clobbered the quarterly update with similar problem as a symptom. Had to reapply (fix) the quarterly update.
close your emulator and delete the snapshot that is in the hyper-V manager
run the emulator again and see if it is working appropriately
(The snapshot, in this case holds the bad response of the emulator. once you delete it and run the emulator, it again reforms to hold the actions where the emulator could work properly)
I am running visual studio 2013 with windows 8.1 pro , I have enabled hyper-v from bios and enable it from program and features also. Firstly when I run my project it gives message like this
after that when I clicked retry it gives this deployment error
Need help in solving this.
Try running visual studio 2013 as an administrator this sometimes helps fix the permission issue running the emulator the first time.
After checking in that textbox where you have to add your lap to the Hyper-V Administrators, just try restarting the machine.
Have a look over here
You should try out these too
1.Run VS 2012 as administrator.
2.Open Hyper-V Manager and check the Windows Phone Emulator Internal Switch from Virtual Switch Manager. Remove the emulator switch and start a new instance of the emulator.
3.If your host computer has a WLAN connection, you should check whether it is running fine or not.
4.If your host computer is in a dedicated network, you can do a wired tethering and create a peer to peer network with another computer. Enable unrestricted internet in one of the systems, share the connection with the other computer, the emulator running in that, will also get the shared internet.
When I try to run the app via Visual Studio 2012 Express for Windows Phone I get the error message:
The application could not be launched for debugging. Ensure that the
target device screen is unlocked and that the application is installed
It worked 10 minutes ago, until I updated with OS version
8.0.10328.78
This was resolved by deploying the solution to the phone first by right-clicking the solution and selecting "Deploy Solution", and then running the app to debug.
I don't know why it's required to deploy the solution first. This wasn't required before the update when I ran the app.
Try either of the following:
1) Developer unlock the phone once more
2) Uninstall your application from the phone by hand, and build it again