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>
PingBack from http://testsubdomain.netmoviehost.com/visual-studio-2008-and-net-framework-35-setup-log-files/
I wrote a post yesterday with a list of the names and locations of all of the log files produced during
Is it save to delete VSMSILog*.txt files after installation is complete? My VSIMsiLog*.txt file is 55MB...
Hi Peter - Yes, after a successful installation it is safe to delete this log file and any of the other logs from your system in order to reclaim disk space.
Below is the first line of the VS2008 log file
[08/18/07,17:16:15] Microsoft Visual Studio 2008 64bit Prerequisites (x64):  e:\setup\..\wcu\64bitprereq\x64\vs_bsln.exe could not be unpackaged because it is not a cabinet.
As a consequence, nothing is installed.
The download went fine, as did the burn to CD, so that looks ok.
I am running Vista Home Premium 64 bit and have tried to install 5 times over the past week or so, changing/removing things as I find possible answers in various places, but still stuck.
Hi HCM - Do you get any error if you try to run that vs_bsln.exe directly from the DVD? Can you also try to copy the contents of the DVD to your hard drive and install it from there to see if that helps workaround this error?
I have tried running from a hard drive, same problem. If I try to run vs_bsin.exe directly from the DVD I get an error message stating that I may have the wrong version. It can't seem to determine whether or not I need x64 or x32, even though it is in the X64 pre reqs (where it should be I think). This error message does not come up if I try to install from hard drive or dvd, but I do get the error message outlined in my first post.
Hi HCM - Can you let me know the exact error message you receive when you try to run the x64 version of vs_bsln.exe directly after copying the file to your hard drive? And just to confirm, you are running on an x64 computer that has the x64 version of Windows installed on it, correct?
This error sounds like possible DVD corruption, so can you check to see if there are any scratches or dust on the back of the DVD and gently clean it and see if that helps? If that still doesn't help, you may need to try to re-burn the DVD.
My team owns the installation experience for Visual Studio 2008 and the .NET Framework 3.5. One difficulty
PingBack from http://msdnrss.thecoderblogs.com/2007/08/20/how-to-report-an-installation-or-setup-problem-with-vs2008-beta-or-net-framework-35-beta/
Yes I can confirm that i am running a 64 bit version of Vista:
From Control Panel\System>>>
PROCESSOR:AMD (Athlon) 64 X2 Dual Core processor 4400 (@2.48 GHz)
SYSTEM TYPE: 64-bit operating system
(Am I right in thinking if the setup program does not see a 64 bit system it would not try to install X64 Prereqs?)
The error message seen when I try to run the program from hard drive is as follows:
Error message is:
The version of this file is not compatible with the version of Windows you are running. Check your computer's information to see whether you need an x86(32-bit) or x64(64-bit) version of the program, and then contact the software publisher.
Hope this makes sense to you.
Hi HCM - Correct, setup detects your processor architecture (x86, x64 or ia64) and it will not attempt to install the x64 prerequisite package unless you are running on an x64 OS. However, the error you are receiving seems to indicate that you are attempting to run this package on a non-matching processor architecture.
Could you please use the tool listed at http://blogs.msdn.com/astebner/archive/2007/08/01/4172276.aspx to gather a list of all of the VS 2008 beta 2 log files and then send me the resulting cab file so I can take a look and see if I can figure anything out? You can send the cab file to Aaron.Stebner (at) microsoft (dot) com.
I have e-mailed you the log files as requested.
Could you please post an answer if you figure this out? I have the same issue.