I have Visual Studio 2012 Pro and Windows 8 Pro. I went to install the Windows 8 SDK, and it installed fine on one of my computers, on which I installed the SDK before installing the Visual Studio 2012 Update 1. But on my second computer, where I installed the Visual Studio 2012 Update 1 before the SDK, I got the following error: KB2744908 Element not found.
Not sure if I would worry about this, or not.
I've attached a screenshot, so you can see the issue. Thanks!
It seems to have fixed itself. After rebooting and allowing the installer to finish after reboot, the SDK works fine. I have successfully created, edited, built, and deployed an application (albeit it was very simple) using the SDK.
Related
I'm working on a Xamarin cross platform project. There is a Android and WinPhone 8 project yet. Everything worked fine. Now I moved to project to another PC. I'm working with Windows 8 and Visual Studio 2015 community version.
I installed the Windows Phone SDK 8 and tried to load the project in Visual Studio. The Android project is ok but on the WinPhone project there is written (unavailable) in the project explorer but the files are in the correct directory.
I also tried to install a Windows Phone 8 SDK update but I always get the message "It needs Visual Studio 2013 or Visual Studio 2012 Update 4 to install this". I also installed Visual Studio 2013 but still get the message.
Did I miss something to install? Already tried to Repair Visual Studio 2015 but it's still the same.
Ok I solved the problem. It's so ridiculous. The SDK and Visual Studio have to be the same language. Otherwise it will not work... well played Microsoft, well played...
Relevant Visual Studio Version Information -
Microsoft Visual Studio Community 2015 Version 14.0.23107.0 D14REL
Microsoft .NET Framework Version 4.6.00079
Visual C# 2015 00322-20000-00000-AA127 Microsoft Visual C# 2015
Windows Phone SDK 8.0 - ENU 00322-20000-00000-AA127 Windows Phone
SDK 8.0 - ENU
Microsoft Emulator version installed 10.0.26624
Although in the Device Selector in Visual Studio it says 10.0.1024.0.
If I create a new UWP (Windows Universal App) and try to deploy it to any mobile emulator is fails with
"There were deployment errors. Continue?"
Investigating the output window and error list there is absolutely nothing there.
I can deploy the application when the target is Local Machine.
Hyper V has no virtual machines registered.
Any ideas?
the information you get "Hyper V has no virtual machines registered" suggest that your Hyper-V is disabled.
Try to type in coreinfo-v.exe in your cmd to find out.
Make sure that your processor supports Virtualization otherwise there is nothing you can do.:(
If you follow this link you will find quite a lot of information how to enable Hyper-V in your computer.
It's an article for Windows phone emulator 8.1 but still quite useful.
https://msdn.microsoft.com/en-us/library/windows/apps/jj863509(v=vs.105).aspx#coreinfo
I have the Windows Phone 8.1 SDK on my dev pc installed together with VS 2013 Community Update 4. I need to open some WP 8.0 projects, but I can't do that without having WP 8.0 SDK installed, give me that error:
I tryed to download the Windows Phone SDK 8.0 from Microsoft site but when I lunch the istaller give me that error:
How can I resolve that problem? If I go to the link didn't explain nothing.
Regards,
Roberto
The error message is self-explanatory, you need a 64bit OS (x64) but you are running a 32bit one (x86).
I think that the reason why this happens is because your VS2013 version is x86 and you downloaded the x64 version of WP8 SDK.
Try the following instead of downloading the SDK and manually installing it.
Right-Click on Start Button
Open Programs and Features.
Find Microsoft Visual Studio 2013.
Click on it and Click Change.
Select Modify.
Choose the Windows Phone 8.0 SDK from there and click Update.
I've have a strange error with Windows Phone Emulator.
Last time I used Visual Studio 2013 and everything worked fine.
Recently I try Visual Studio 2014 CTP parallel with VS2013 but now I cannot debug Windows Phone app with Emulator from VS2013.
The app deploy successful and I can run it from Emulator but when I hit F5 VS always show:
"The application could not be launched for debugging. Ensure that the target device screen is unlocked and that the application is installed."
I've removed all Visual Studio 2014 CTP and Emulator 14 but it's not effect.
Could anyone here have similar error?
Please show me what problems is?
Thanks in advance.
The only time I have seen this error was when the app is already installed on device\Emulator, I had to remove the app , then hit F5 to work.
I just installed Visual Studio 2013 on my machine (which runs Windows 8.1 Enterprise Build 9600). I checked to include the Windows Phone 8 SDK option during install.
Once complete, I launched VS and tried a new Windows Phone App project.
Created and built fine. However. when I tried to run on the emulator, I get the error:
Xap packaging failed. Cannot access a closed Stream.
... and ...
Could not find file 'c:\users\wade\documents\visual studio 2013\Projects\DataBoundApp1\DataBoundApp1\obj\Debug\XapCacheFile.xml'. Please rebuild the solution and try again.
Tried a clean and rebuild but still occurs. Also happens with the data bound app project.
So, I tried installing some of the SDK updates found here: http://developer.windowsphone.com/en-us/downloadsdk. All installed without a problem; however, when I tried again I got the same error.
Note: the emulator starts and runs just fine. The problem is creating the phone package and deploying to the emulator.
I'm not sure how to fix. Anyone have this issue?
UPDATE:
I have tried reinstalling the Windows Phone 8.0 SDK and all the updates. I should note that I also have VS 2012 installed and I also cannot create a Windows Phone 8 app in VS2012.
Here's an image of the WP8 stuff installed:
I resolved this issue by downloading the full Windows Phone 8.0 SDK ISO and installing (followed by a repair on the two updates).
I wish I could better explain how my machine got into this state. My suspicion is it's because I already had VS2012 installed on the machine and VS got into a confused state.
Total time spent? 4-5 hours.