1 reply to this topic

[vlasta]

Hi all,

I have an application built in VS 2005 Beta2, consisting of several COM dlls. The .msi setup package is also created in VS 2005.

After I install it on Vista and run it, the installer is automatically
started again, trying to repair it, cycling indefintely (well, longer, than I
had the patience to wait). What could be wrong? Can I somehow find out why is the installer trying to repair a freshly installed app?

The application has no problems on Win 98, ME, NT4, 2000, XP, XP 64bit.

What I have tried so far:
1. changing the registration from vsrdpCOM to vsrdpCOMSelfReg - did not help

2. not using installer: copying files manually and registering them using regsvr32 - works

3. using older installer built in VS 2005 Beta1 - works

The application installs side-by-side version of C++ runtime
library into WinSxS using the mergemodule, that comes with VS. All other
files are installed in Program Files folder and all of them are built in
VS2005 except SHFOLDER.dll.

When upgrading to VS 2005 Beta2, a 'SignManifest=true' was added to almost
all my .vcproj files. There seems to be an extra entry in COM classes
registration records with a checksum or whatever. Could this be the cause of
problems?

Thanks for any suggestions,
Vlasta

[Zweitze]

To find out why Windows thinks a repair is necessary, look at the Application EventLog: it shows the ComponentID of the broken component.