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.
The official .NET Framework 4 deployment guides for application developers and system administrators have been posted 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 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 and that will need to incorporate the .NET Framework 4 into their installation process. It contains the following information:
Microsoft .NET Framework 4 deployment guide for administrators
You can find the administrator deployment guide at the following location:
The administrator deployment guide is targeted at system administrators that manage software installation on corporate networks and who want to plan a deployment of the .NET Framework 4 to networks that they manage. It contains the following information:
Yesterday, we released several samples and mini-games to help you get started using the Windows Phone Developer Tools CTP (which includes the XNA Game Studio 4.0 CTP) to create games for Windows Phone 7 Series. Here is some additional information about the samples and where you can download them:
<update date="9/1/2012"> Fixed broken links to samples. </update>
Back in January, I wrote a blog post about errors that can occur while trying to install TurboTax 2009 because some .NET Framework 3.5 files and/or registry keys are missing from the computer. Since then, I’ve heard from some people who have run into problems similar to what I described in my original blog post, and I wanted to provide a couple of updates based on what I’ve learned since then in case the information in my original blog post does not end up being helpful.
How to bypass the .NET Framework verification check in TurboTax 2009 setup
A few people who contacted me reported that they have the CD-based version of TurboTax 2009, and they were able to install by running the installer in the TurboTax 2009 Installer sub-folder instead of running the setup.exe at the root of the disc. It appears that the .NET Framework verification check happens in the main setup.exe and that this check can be bypassed by running the installer in the sub-directory instead.
I have also heard from people who downloaded TurboTax 2009 setup from the Intuit web site instead of buying the CD, and that they couldn’t find a way to bypass the .NET Framework verification check with the downloaded version. I haven’t yet been able to look at the structure of the downloaded version of the TurboTax 2009 setup package to see if there is a way to bypass the check in that version or not.
Verification error on non-English versions of Windows 7
Multiple people have reported problems with .NET Framework 3.5 verification during TurboTax 2009 setup on non-English versions of Windows 7. There is a known problem with the verification logic used by TurboTax setup that is causing it to incorrectly search for some English files and registry keys even on non-English versions of Windows 7. I fixed this issue in the verification tool on my blog, but it is still a problem within TurboTax 2009 setup.
If you run into this problem, I first suggest that you try to bypass the .NET Framework verification check by using the information listed above in this blog post.
If the bypass option does not work or if you have the web download version of TurboTax 2009 instead of the CD version, then you can download this zip file that contains the English files and registry keys that will be reported as missing by the TurboTax 2009 installer on non-English versions of Windows 7 and copy them to the locations that are expected by the TurboTax 2009 verification process.
You can do the following to use this zip file:
If neither of the above is helpful
If you still see errors related to the .NET Framework 3.5 SP1 during TurboTax 2009 setup even after trying the above, then please use the TurboTax verification tool and the steps described in my previous blog post to try to narrow down which files and/or registry keys that TurboTax 2009 setup is reporting as missing on your computer.
If you are unable to locate the sources of the errors by looking at the verification log files yourself, you can post your verification log files to a file server (such as http://skydrive.live.com) and reply to one of my blog posts with a link to the logs and I will try to take a look and see if I can figure out what is missing.
TurboTax 2009 errors that do not involve installation or verification of the .NET Framework 3.5 SP1
I have heard from some people who have been able to solve .NET Framework 3.5 SP1 installation and verification issues and proceed with TurboTax 2009 setup, but who have then run into issues later on in the TurboTax setup process or who have run into issues trying to run TurboTax after the installation process completes. Unfortunately, the only set of issues that I have the expertise to help troubleshoot are the ones related to .NET Framework installation and verification. If you are running into other issues installing or running TurboTax, then I suggest that you search for similar issues on the TurboTax support site and/or contact the TurboTax technical support team for more detailed troubleshooting assistance.
<update date="4/13/2010"> Added a note about creating the folders if they do not exist for the non-English Windows 7 scenario </update>
As Soma announced on his blog yesterday, the final versions of Visual Studio 2010 and the .NET Framework 4 have been released and are now available for download. Here are some links to help you get started:
.NET Framework 4 links
Visual Studio 2010 links
Visual Studio 2010 Express Editions links
As announced on the Windows Phone Developer Blog, a Windows Phone Developer Tools (WPDT) CTP Refresh (which includes an XNA Game Studio 4.0 CTP Refresh as well) was released for download today.
Getting Started links
Here are links to help you get started installing and using the Windows Phone Developer Tools CTP Refresh:
Please make sure to look at the Breaking Changes section of the release notes – there are a few key issues there that you will need to keep in mind if you have projects created with the WPDT CTP, including the following:
The primary reason for the CTP Refresh is to support Windows Phone development in the final release of Visual Studio 2010 instead of in the VS 2010 RC. For an overall list of what’s new in the CTP Refresh, I encourage you to take a look at the links in this blog post and this MSDN topic.
The CTP Refresh includes the following XNA Game Studio 4.0 changes:
How to install
Here are steps you can use to install the Windows Phone Developer Tools CTP Refresh
If you encounter Windows Phone Developer Tools CTP Refresh setup failures
If you run into an installation or uninstallation failure for the Windows Phone Developer Tools CTP, 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.
This tool does not gather XNA Game Studio 4.0 setup log files, so if your setup failure is caused by the XNA Game Studio 4.0 component, you’ll need to gather those logs separately by zipping up all of the logs in the folder named %temp%\XNA Game Studio 4.0 Setup\Logs.
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.
If you run into uninstallation issues with the WPDT CTP or the CTP Refresh, you can use the cleanup tool described at http://blogs.msdn.com/astebner/pages/9544320.aspx to remove XNA Game Studio or the Windows Phone Developer Tools.
Now that the final version of the .NET Framework 4 has been released, I have posted updated versions of my sample .NET Framework detection code.
I previously updated the sample code to be able to detect the .NET Framework 4 client and full profiles. However, the previous sample code would detect that the .NET Framework 4 was installed even if a pre-release version was installed instead of the final version. In this update, I’ve added the ability to detect the final version of the .NET Framework 4 and filter out pre-release versions.
You can find information about the sample .NET Framework detection code and download links in the article at http://blogs.msdn.com/astebner/pages/9763379.aspx.
Now that the final versions of Visual Studio 2010 and the .NET Framework 4 have shipped, Peter Marcu has posted an updated version of an article he wrote back in the beta 2 timeframe that describes improvements made to the .NET Framework 4 installer to improve the robustness, size and performance.
You can find the updated article at http://blogs.msdn.com/pmarcu/archive/2010/04/15/the-net-framework-4-installer-improvements.aspx, and I encourage you to take a look at it to learn more behind-the-scenes details about .NET Framework 4 setup.
As I noted in my previous blog post, the final versions of Visual Studio 2010 and the .NET Framework 4 have shipped. I wanted to also briefly note that the Windows Phone Developer Tools CTP that was released a month ago at the MIX10 conference is not compatible with the final version of VS 2010. You must continue using the VS 2010 release candidate build in order to use the Windows Phone Developer Tools CTP.
Charlie Kindel posted some information on the Windows Phone Developer Blog with options you can pursue in the meantime, and he also discusses the timing for an upcoming refresh of the Windows Phone Developer Tools that will work with the final release of VS 2010.