Thoughts about setup and deployment issues, WiX, XNA, the .NET Framework and Visual Studio
All postings are provided AS IS
with no warranties, and confer no rights. Additionally, views expressed
herein are my own and not those of my employer, Microsoft.
As announced earlier today on the Windows Phone Developer Blog and the Visual Studio Blog, the Windows Phone SDK 8.0 is now available for download. Here is some information to help you get started installing and using the Windows Phone SDK 8.0.
The Windows Phone SDK 8.0 is available in the same set of languages as the Windows Phone SDK 7.1 – Chinese (Simplified), Chinese (Traditional), English, French, German, Italian, Japanese, Korean, Russian and Spanish.
Documentation and getting started links
Installing the Windows Phone SDK 8.0
The Windows Phone SDK 8.0 must be installed on a Windows 8 x64 computer, and the computer must have a processor that supports Second Level Address Translation (SLAT) in order to fully function. You can use the tool at https://slatstatuscheck.codeplex.com/ to determine if your processor supports SLAT. If you install on a computer with a processor that does not support SLAT, then Windows Phone SDK 8.0 setup will complete, but the Windows Phone 8 emulator will not function correctly.
Unlike in previous releases, Windows Phone SDK 8.0 setup will not block attempts to install on Windows Server 2012. However, the Windows Phone 8 emulator will not function correctly on Windows Server 2012.
If you run into an installation or uninstallation failure for the Windows Phone SDK 8.0, you can use the log collection tool to gather your setup log files. This log collection tool will create a file named %temp%\vslogs.cab. Once you have gathered your setup log files, you can upload them to a file server of your choice (such as http://skydrive.live.com), and post a link to the log files in the forums to get additional support.
Notes about XNA Game Studio
The Windows Phone SDK 8.0 includes a subset of the XNA Game Studio 4.0 Refresh product. Specifically, it only allows you to develop Windows Phone games that use the XNA Framework. You can see more information about what XNA Framework functionality is supported in the Windows Phone SDK 8.0 in this documentation topic.
If you are developing Windows games or Xbox 360 games that use the XNA Framework, you must continue to use an edition of Visual Studio 2010 and one of the following products:
Both of the above products can be installed side-by-side with the Windows Phone SDK 8.0.
<update date="10/31/2012"> Fixed documentation links to point to MSDN instead of redirecting through the Windows Phone Dev Center. </update>
The official .NET Framework 4.5 deployment guides for developers and administrators are available on MSDN, and I wanted to provide links here to help raise visibility for them. Here they are along with some additional information about what is contained in each of them:
Microsoft .NET Framework 4.5 deployment guide for developers
You can find the deployment guide for application developers at the following location:
The deployment guide for application developers is targeted at developers creating applications that depend on the .NET Framework 4.5 and that will need to incorporate the .NET Framework 4.5 into their installation process. It contains the following information:
Microsoft .NET Framework 4.5 deployment guide for administrators
You can find the administrator deployment guide at the following location:
The administrator deployment guide is targeted at system administrators who want to deploy the .NET Framework 4.5 across a network by using System Center Configuration Manager (SCCM). It contains the following information:
A little while ago, I posted an introduction to a new .NET Framework Repair Tool that can be used to diagnose and repair .NET Framework 4 setup issues. An updated version of the repair tool has been released today to add support for diagnosing and repairing issues with .NET Framework 2.0 SP2, 3.0 SP2 and 3.5 SP1 setup. The repair tool can identify and fix issues with the installation of MSI-based versions of the .NET Framework, but it cannot fix issues related to versions of the .NET Framework that are installed as a part of Windows.
If you run into installation issues with the MSI-based versions of the .NET Framework 2.0 SP2, 3.0 SP2, 3.5 SP1 or 4, I strongly encourage you to download the .NET Framework Repair Tool and run it to see if it resolves your issue before resorting to trying the .NET Framework cleanup tool. Here are links that you can use to find additional information about the .NET Framework Repair Tool: