VisualStudio integration fails on Vista64

Hello,

the installed VS is 2005 standard, UAC is enabled on that vista64. The installation of FTN95 went fine (no errors reported) except that the VisualStudio integration failed (the button during installation was chooseable and selected).

Looking through the registry keys and comparing against an XP installation, the VS keys are under HKLM\Software\Wow6432Node\Microsoft\VisualStudio\8.0 for vista64 whereas they are under HKLM\Software\Microsoft\VisualStudio\8.0 for XP. The registry keys specific to FTN95 like InstalledProducts\FTN95Project are NOT present anywhere in the registry of vista, though I'd expect the FTN95 installer to report an error if the keys could not be written/verification failed (is there an installation log, or can the installation be started in some verbose mode?).

Thanks.

Did the UAC prompt appear when you first started the install?

Have you tried the install without UAC?

The way to get a log of the plugin install is as follows:

• use WinRAR or 7-zip to extract the ftn95 install executable to a directory

• run the plugin install from the command line with:

  msiexec /I FTN95_VS_PLUGIN_2005.msi /L c:\install.log

This should produce a log file which hopefully should provide more information. I would try this from a normal command prompt and also from an administrator command prompt (use Run as Administrator when starting the prompt).[/code]

Did the UAC prompt appear when you first started the install?

No it didn't.

Have you tried the install without UAC?

No and actually I'd prefer to leave it on.

The way to get a log of the plugin install is as follows:

• use WinRAR or 7-zip to extract the ftn95 install executable to a directory
• run the plugin install from the command line with:

Does not work, results in this error (both regular and admin console):

Microsoft Visual Studio 2005 must be installed in order to install FTN95 for Microsoft Visual Studio 2005. Please ensure Visual Studio 2005 is installed and run setup again.

Anyways, during installation there's a log file created in AppData\Local\Temp which shows the same error, so it just wasn't visible (I was expecting a message box on error).

I just noticed that the Customer Information dialog has 'root' as user name which is a bit odd, as I'm not logged in as that user (this account exists though).

I am not sure the Wow6432Node bit in the registry makes much difference -- the wow part of the 32-bit emulation handles the remapping. Both VS and the plug-in installer sees a path that it would in 32-bit Vista. As it's HKLM the installer would have to be run with admin privileges -- I assume you are running from an admin account?

Both VS and the plug-in installer sees a path that it would in 32-bit Vista.

That's what I assume as well (both are 32bit), yet VisualStudio works fine as is.

As it's HKLM the installer would have to be run with admin privileges -- I assume you are running from an admin account?

I don't know how VisualStudio was installed, presumably by a regular user account if that's possible at all (as the Wow6432 redirection worked there). The current account I'm trying to install the FTN95/VisualStudio integration with is an admin one, but I've also tried it with a degraded, regular-user account with exactly the same issue (that is starting the .msi results in the 'VS not found' message; using the regular installer aborts with 'not enough privileges').

I suspect Visual Studio was installed with admin privileges. Without a service pack it will not even run on Vista 64 without full admin rights. Are you right clicking the installer and doing 'run as admin'?

Are you right clicking the installer and doing 'run as admin'?

Yes, this doesn't work as well.

Without a service pack it will not even run on Vista 64 without full admin rights.

The VS installation is 2005/SP1.

Some testing with a 32bit registry viewer, used account is admin, UAC enabled: when starting the reg viewer (NOT the regedit that comes with vista) the HKLM/SOFTWARE/Microsoft/Visual Studio/8.0/ subkeys are all visible, that is the WOW6432 redirection works fine. The same is true when right-clicking the reg viewer and using the 'run with admin rights' entry.

It seems like the execution of the .msi takes place in 64bit (thus the WOW6432 redirection is not active), but I don't see a way to verify this or fix/work around it. Any ideas welcome.