VC++ Merge Modules, Major Upgrade, More Troubles.

[Superfreak3]

Hi all,

Here's another problem, at least I think its a problem....

In our previous release we had included the VC++ 2008 runtime via Merge Modules. We also have them included in the latest release.

However, post install, a repair is fired. After further investigation of the Event Log and .msi, I found that the problematic component pointed to one of the Merge Modules.

Also, from the log I got this...

[CODE]MSI (c) (C8:50) [17:40:33:205]: skipping installation of assembly component: {634088A3-D67E-336D-9425-767BA6907C74} since the assembly already exists
MSI (c) (C8:50) [17:40:33:205]: skipping installation of assembly component: {3C582984-7607-3E35-A337-D3D327097351} since the assembly already exists
MSI (c) (C8:50) [17:40:33:205]: skipping installation of assembly component: {229E8F96-1AE0-32E6-8428-D2CBCA122740} since the assembly already exists
MSI (c) (C8:50) [17:40:33:205]: skipping installation of assembly component: {CB438DD9-2B1B-32E0-9AA6-D6DA82CE9D97} since the assembly already exists
MSI (c) (C8:50) [17:40:33:205]: skipping installation of assembly component: {6D321E57-3E99-3B87-BF23-2CDFF3361CB4} since the assembly already exists
MSI (c) (C8:50) [17:40:33:205]: skipping installation of assembly component: {AE56AAF5-F3C0-3D4B-8859-A1E50A3E27BF} since the assembly already exists
MSI (c) (C8:50) [17:40:33:205]: skipping installation of assembly component: {63E949F6-03BC-5C40-A01F-C8B3B9A1E18E} since the assembly already exists
MSI (c) (C8:50) [17:40:33:205]: skipping installation of assembly component: {98CB24AD-52FB-DB5F-A01F-C8B3B9A1E18E} since the assembly already exists[/CODE]

What the heck is going on here? If it's not something I'm doing wrong, its got to be a bug, no?

Our prevous install was made with Wise so maybe the Merge Modules used with that have a higher version that what is included with install shield. ??

Any help is GREATLY APPRECIATED!

Thanks in advance!!

[weakness]

Do you know the following MS's KB?

An assembly in the global assembly cache or SxS is missing after you perform a major upgrade by using a Windows Installer package
http://support.microsoft.com/kb/905238/en-us

Apparently, Major upgrade by using VC++ Merge Modules is not recommended.

So,you may want to use InstallShield prerequisite in order to launch VC++ redistributable package, rather than use Merge Modules.

[Superfreak3]

Unfortunately I can't wrap our client software installer in a setup.exe with a prerequisite. We have an update detection widget that, if needed, will fire our client product .msi.

It's funny, because with Wise, we deployed VC++ Merge Modules and I don't recall this happening with our Major Upgrades at that time.

I guess the only alternative is that custom IT depts will have to ensure VC++ Runtimes are installed prior to launching our installation.