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 heard from a customer who ran into an interesting issue during Visual Studio 2008 setup that I hadn't seen until now. I wanted to post a description of the issue, how we diagnosed it and how to work around the issue in case anyone else runs into a similar issue in the future.
Description of this issue
On this customer's system, the Web Authoring Component prerequisite component failed to install and Visual Studio 2008 setup failed as a result. There are many possible causes for this type of failure, so we need to dig deeper to try to find the exact cause of the failure.
How to diagnose this issue
Visual Studio 2008 setup runs the Web Authoring Component setup package in silent mode, so the next step is to take a look at the log file for the Web Authoring Component to narrow down the issue further. This issue will cause the following information to be written to the log file for the Web Authoring Component (named %temp%\SetupExe(*).log):
Catalyst valid path check failed: The path c:\Program Files\\Microsoft Web Designer Tools is invalid
Notice that there is an extra backslash between Program Files and Microsoft Web Designer Tools in this log file. I had the customer check their registry and we found that the path to the Program Files folder was being stored there with a trailing backslash, but Windows typically stores the path to Program Files and other system folders without trailing backslashes.
In this scenario, it is also possible to run Web Authoring Component setup directly from <VS install path>\WCU\WebDesignerCore\WebDesignerCore.exe in order to see a specific error message instead of looking at the log files.
How to work around this issue
To work around this issue, you can change the value that Windows uses for the Program Files directory on your system by doing the following:
One note about this issue - the Web Authoring Component setup package uses the same setup wrapper as the Office 2007 family of products. It appears that other Office 2007 products may have similar installation errors if the ProgramFilesDir value has a trailing backslash like this.
PingBack from http://msdnrss.thecoderblogs.com/2008/01/14/web-authoring-component-can-fail-during-vs-2008-setup-if-program-files-has-a-trailing-backslash/
PingBack from http://geeklectures.info/2008/01/13/web-authoring-component-can-fail-during-vs-2008-setup-if-program-files-has-a-trailing-backslash/
Thanks very much for publishing this. I had this very problem and probably never would have
figured out what caused it.
PingBack from http://www.bdwakefield.com/idevelop/2008/12/15/web-authoring-component-failing-during-vs-2008-set-up/
Nivel: Inicial Tema: Visual Studio Autor: César Reneses – Coordinador Albacete DotNetClub A pesar de
Nivel: Básico Tema: Visual Studio Autor: César Reneses – Coordinador Albacete DotNetClub   A pesar
Nivel: Básico Tema: Visual Studio Autor: César Reneses – Coordinador Albacete DotNetClub A pesar de llevar