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 installers for the .NET Framework 3.5 and Visual Studio 2008 chain several different prerequisites and optional components behind the scenes. If one of these setups fails, there are numerous possible causes due to the number of packages being chained behind the scenes. The following provides a list of log files created by the setup wrappers for each product and the child packages that are chained in during installation.
.NET Framework 3.5 setup log files
The following is a complete list of log files that can be produced during .NET Framework 3.5 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.5 setup.
Logs produced by the .NET Framework 3.5 setup wrapper:
Logs produced by the packages chained during .NET Framework 3.5 setup:
Visual Studio 2008 setup log files
The following is a complete list of log files that can be produced during Visual Studio 2008 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 Visual Studio 2008 setup.
In addition to the logs listed below, Visual Studio 2008 setup can produce the logs listed above for the .NET Framework 3.5 because the .NET Framework 3.5 is a prerequisite that is chained in during Visual Studio 2008 setup if it is not already installed on the system.
Logs produced by the Visual Studio 2008 setup wrapper:
Logs produced by the packages chained during Visual Studio 2008 setup:
Logs produced by the packages chained during Visual Studio 2008 Express Edition setups:
Logs produced by the MSDN for Visual Studio 2008 setup wrapper:
Logs produced by Visual Studio 2008 SP1:
If you run into any issues while installing the .NET Framework 3.5, Visual Studio 2008 or MSDN for Visual Studio 2008 and plan to report setup 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="10/4/2007"> Added a log file to the .NET Framework 3.5 list for the WCF custom action that I missed previously </update>
<update date="1/11/2008"> Added Silverlight log files to the list for VS 2008 Express Editions since it was added as a chained component between the time I wrote this blog post and the time that VS 2008 shipped. </update>
<update date="5/23/2008"> Added log file information for Visual Studio 2008 SP1 </update>
<update date="11/20/2009"> Fixed broken link to the product feedback site. </update>
Hi LamCo - There isn't enough information in this log file to narrow down the cause of the setup failure that you're running into. Can you please use the tool described at blogs.msdn.com/.../6458047.aspx to gather all of your VS 2008 setup log files, then post the file %temp%\vslogs.cab that this tool creates on a file server (such as http://skydrive.live.com), then reply back here with a link that I can use to download your log files and take a further look?
setup is looking for vcredistmin x_86.exe
please insert microsoft visual studio 2008 prifessional ENU ,insert disk1 now
path---this path is not valid
i have this setup in my pen drive and then copy in drive G
Hi Anu - Are you getting this error during initial installation or during repair? If it is initial installation, I'd suggest trying to re-copy or re-download the files from the original install location because it sounds like one of the files that setup needs is missing or corrupt. If this is during repair, I'd suggest trying to repair from the original location that you installed from instead of using the entry in the Programs and Features or Add/Remove Programs control panel.