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.
A few weeks ago I posted a list of supported command line switches for the new setup wrapper that is used to install the .NET Framework 2.0 and other products in the Visual Studio 2005 family. If you are deploying the .NET Framework 2.0 as part of another setup package, the command line parameters are only one piece of the puzzle. It is also useful to listen to the return codes passed back by the setup package in order to determine if .NET Framework 2.0 setup succeeded or failed.
In general, the return code 0 indicates success, the code 3010 indicates success with a reboot required, and anything else indicates failure.
Here is a list of other return codes that could be generated by the .NET Framework 2.0 setup wrapper along with descriptions of what they mean:
Here are some other error codes that could be returned by the .NET Framework 2.0 setup wrapper, but that are actually generated by Windows Installer and not by the code for the setup wrapper itself:
Please note that I do not list any generic Win32 error codes here. You can use a tool such as errlook.exe (which ships in %ProgramFiles%\Microsoft Visual Studio 8\Common7\Tools if you have VS 2005 installed) or err.exe to translate Win32 error codes.
<update date="12/12/2005"> Added some common Windows Installer error codes to the list </update>
Details about the .NET Framework 2.0 setup packaging Available command line switches for .NET Framework
A while back, I posted a list of possible return codes for the .NET Framework 2.0 . I recently found
This guide is intended to serve as a collection of links to articles, tools, tips and tricks that explain