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.
I wrote a post yesterday with a list of the names and locations of all of the log files produced during Visual Studio 2008 and .NET Framework 3.5 setup. As you can see in that post, the list of possible log files is very long, and that makes it annoying when attempting to gather the logs and send them back to Microsoft so that we can help troubleshoot installation issues.
Fortunately, Sandhya, a colleague of mine, has written a tool that will automatically gather all of the VS 2008 and .NET Framework 3.5 setup log files it can find from your system and create a cab file containing them so you have a single compressed package that can be sent to Microsoft for troubleshooting purposes.
How to use the Collect tool
The tool can be downloaded from http://go.microsoft.com/?LinkId=8967043. It is a Win32 console application, so you can extract it from the zip file and double-click on it to run it. It will create a file named %temp%\vslogs.cab on your system after it has gathered all of the log files.
Note - after the tool finishes running, you can get to your %temp% folder to find the file vslogs.cab by clicking on the Start menu, choosing Run, typing %temp% and clicking OK.
What to do if the Collect tool does not work correctly on your system
If the tool encounters any problems, you can do the following to re-run it from a cmd prompt and see more detailed error information:
<update date="5/23/2008"> Updated link to log collection tool to point to the new location </update>
Tool to collect VS2008 and Fx 3.5 setup logs
To collect the logs please follow the steps found on aaronste’s blog: Tool to automatically collect and
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/
I just noticed this post on Bret Grinslade's blog that I wanted to link to here to help raise visibility.
I just noticed this post on Bret Grinslade's blog that I wanted to link to here to help raise visibility
PingBack from http://testsubdomain.netmoviehost.com/report-vs-2008-or-net-framework-35-beta-installation-issues/
PingBack from http://msdnrss.thecoderblogs.com/2007/08/28/report-vs-2008-or-net-framework-35-beta-installation-issues-directly-to-the-setup-team/
I previously wrote about a log collection tool that will automatically gather and cab up Visual Studio
We've been seeing some issues where VS 2008 crashes when creating a new WPF project. The underlying issue
PingBack from http://msdnrss.thecoderblogs.com/2007/12/04/visual-studio-2008-rtm-crashing-when-creating-a-wpf-project/
Step 1. Follow Aaron Stebner's blog: http://blogs.msdn.com/astebner/archive/2007/08/01/4172276.aspx Step
Step 1. Follow Aaron Stebner's blog: http://blogs.msdn.com/astebner/archive/2007/08/01/4172276.aspx