Project Glidepath

Having recently installed Vista RC2 I have been eagerly installing all my favourite applications: Office 2007, Visual Studio 2005, Orcas VS extensions, WF designer extensions, Live Messenger, Guidance Automation Extensions/Toolkit. Most of these installed without a hitch, although I did get continually prompted to allow Administrative permissions. Note: I did NOT have to disable User Access Control (yet).

Yesterday I got an email from the Project Glidepath team announcing that v2 is now available for download, so I eagerly downloaded it. After installing the Guidance Automation Extensions (although they include the Dec 2005 release, I had already installed the most recent release) I proceeded to install Project Glidepath. Half way through the install fails, “Error 2869”. This seems to relate to the infamous User Access Control(UAC). Work around is to create a batch file with the following lines:

msiexec /i ProjectGlidepathRepositoryManagerSetup.msi
msiexec /i ProjectGlidepathMicroISVFactorySetup.msi

Then right-click the batch file and select “Run as Administrator”. This will get the installer to work. However, the UAC issues are not over yet. The post-installation instructions suggest running Visual Studio 2005 and creating a new Project Glidepath project, from which you can “update” to retrieve the latest guidance information. Unfortunately, what they don’t tell you is that you MUST run Visual Studio as administrator, otherwise the database can’t be created and you won’t be able to update. Again, this can be done by right-clicking on Visual Studio 2005 in the start menu and selecting “Run as Administrator”.

Well, back to “synchronising” project glidepath – will hopefully have an update as to what is actually included once this has completed.

Leave a comment