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 installer for the .NET Framework 3.0 (formerly named the WinFX runtime components) chains several different MSIs and Windows hotfixes behind the scenes. If this setup fails, there are numerous possible causes due to the number of packages being chained behind the scenes.
The following is a complete list of log files that can be produced during .NET Framework 3.0 setup. This list may vary depending on what OS you are installing on, what processor architecture, and what prerequisite components were already installed on the system prior to running .NET Framework 3.0 setup.
Logs produced by the .NET Framework 3.0 setup wrapper
Logs produced by packages chained during .NET Framework 3.0 setup
Logs produced by the .NET Framework 3.0 language pack setup wrapper
Logs produced by packages chained during .NET Framework 3.0 language pack setup
Log files will be located in the %temp% directory on the system during installation. When setup completes successfully, the logs produced by the setup wrapper and the log file named vsmsilog*.txt are moved to a new folder located at %windir%\Microsoft.NET\Framework\v3.0\<product name>\Logs. The <product name> will be Microsoft .NET Framework 3.0 or one of the language packs (for example - Microsoft .NET Framework 3.0 x64 Language Pack - FRA).
If you run into any issues while installing the .NET Framework 3.0 and report issues to Microsoft via the product feedback site or the MSDN Forums, please locate and include any of the above log files if possible because it will make it easier for us to debug the failures and find root causes and workarounds.
<update date="11/9/2006"> Added a list of log files for .NET Framework 3.0 language packs and a couple of other log files that I missed originally. Also added locations where the logs can be found. </update>
Hi Ziaulla - This type of error typically means that there is something wrong with the version of the .NET Framework 2.0 on your computer. I'd suggest that you try to repair the .NET Framework 2.0 and see if that resolves this error. If not, then you may need to uninstall + re-install the .NET Framework 3.5, 3.0 and 2.0 using steps like the ones at blogs.msdn.com/.../8108332.aspx.
Hopefully one of these suggestions helps in your scenario.