Guys (and girls),

we ran into a strange issue here, so hoping one of you can help...

for one of the in-house applications we have here, which regularly gets updated, we've been using an automated build tool to provide regular MSIs. My colleague has recently installed a new build machine for this purpose. Only difference with the old one is the version of InstallShield, old one was 2010, this one has 2011 on it.

Now when he did a static scan for dependencies in Installshield 2010, on his old machine, he'd get a mention of the file microsoft.mshtml.dll needing to be added as a dependency of one of the files in the package, Installshield would find the file and include it, and all would be well.
The same scan, of the same template ism, in Installshield 2011 however, also detects the need to add this same dll, but gives us a ***missing file*** warning, even though the file is most definitely present on the new build machine, and registered into the GAC.

Has any of you ever faced this issue and managed to solve it, or been able to confirm it's a bug in the new InstallShield or anything like that? Or is this just some .NET related thing we're missing? Both machines have the same .NET versions installed, as well as the framework SDK v2.0 and the PIAs

Thanks in advance for any pointers,

PJ
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Pieter! Shame on you! No UAT before blasting the new flavour on to your boxes?
Answered 12/22/2011 by: VBScab
Red Belt

Please log in to comment
0
Ian,

we're talking a new version of an internal build machine for automated package generation here. Internal as in only for the packaging team.
This has no impact on business UAT or Production.

We kept the old machine around, and that's about as 'UAT' as we packagers can get here. [;)]

PJ

EDIT: Come to think of it... this actually IS uat, we just haven't quite reached the 'Acceptance' phase yet.
And another point I didn't mention yet, the old machine was an XP, this one is W7.... might be pertinent... [:D]
Answered 12/23/2011 by: pjgeutjens
Red Belt

Please log in to comment
0
Answered 12/23/2011 by: VBScab
Red Belt

Please log in to comment
0
This couldn't be a case of the merge module paths settings in InstallShield 2011 being incorrect, could it ?

Perhaps you could compare all the InstallShield options settings from the old machine with those on the new one ?

Regards,

Spartacus
Answered 12/23/2011 by: spartacus
Black Belt

Please log in to comment
0
This couldn't be a case of the merge module paths settings in InstallShield 2011 being incorrect, could it ?

We already looked into that, unfortunately that's not it.
On a side note, does any of you know if there is a specific msm that contains this file (microsoft.mshtml.dll)? I haven't found anything on it so far.

PJ
Answered 12/23/2011 by: pjgeutjens
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity