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.
Recently, beta versions of Visual Studio 2008 SP1 and the .NET Framework 3.5 SP1 were released (see announcement posts here and here for in-depth information if you are interested).
As Heath Stewart described in more detail in this blog post, the Visual Studio 2008 service pack has a new setup bootstrapper to provide a unified installation experience, better progress and error handling and fix some of the key issues that affected the Visual Studio 2005 service pack installation experience. One of the outcomes of this new bootstrapper is that some new log files are created that can be useful to help troubleshoot SP1 installation issues.
I previously posted a list of log files that can be produced by Visual Studio 2008 and .NET Framework 3.5 setup. In addition, I posted a link to a tool to automatically gather these log files and create a cab file to make them easier to send via email or attach to bug reports.
As Heath pointed out in this blog post, the information in those posts became a bit out of date with the release of the VS 2008 SP1 beta. I have updated those blog posts to include information about new logs that are being created by VS 2008 SP1 beta setup and will continue to update it if any additional logs are created by the time the final version of VS 2008 SP1 is released. I also updated the version of the log collection tool that is linked in my previous blog post to also collect VS 2008 SP1 beta setup log files.
You can find the most up-to-date version of the Visual Studio 2008 and .NET Framework 3.5 log collection tool at http://go.microsoft.com/?LinkId=8967043. This link will continue to be redirected as the tool is updated in the future as well.
δεν μπορω να εγγαταστησω ενημερωσεις σφαλμα 643