A word of warning to those of you who are using the Wise Application Conflict analysis database and tools...

When it comes to identifying conflicts between packages which contain the same registry keys/items, Wise DOES NOT identify a conflict where one package uses the 'advertising' tables for COM components and another package uses the registry table.

This can result in registry settings being wrongly removed on application uninstall.

This applies to versions of Wise Package Studio up to, and including, version 5.6
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
Yup. Quite true. Conflict Analysis is really MSI Database conflict analysis, not Actual Result conflict analysis. If you have a Custom Action that creates a registry key that conflicts with another app, same problem.

Another case for standardizing the way you do things.
Answered 06/03/2005 by: VikingLoki
Second Degree Brown Belt

Please log in to comment
0
But assuming your components are well designed and your COM registration information (registry or other) is included within the same component as the DLL/OCX itself (the keypath by definition), you most probably won't have an issue. If the GUIDs for the components are synchronised, then the component and all it's resources will only be removed once no more packages are using them.

It is therefore essential to use a repackaging tool that does an excellent job when organising resources into components. Although earlier versions possibly weren't, I believe that the latest versions of Wise Package Studio are pretty good in this respect?
Answered 06/04/2005 by: WiseUser
Fourth Degree Brown Belt

Please log in to comment
0
Yes, I believe that the latest version of Wise (5.6) is supposed to be 'more clever' when it comes to sorting out which registry settings go with which component (and the related file). Problem is that 5.6 hasn't been out that long and we have 100s of packages where this is not the case.

I would have expected Wise conflict analysis to at least identify MSI database conflicts; OK, so they are in different tables, but it's not 'rocket science' to work out the corresponding registry settings. We've had to write our own code to identify such 'conflicts', whereas I would expect it to be part of the Wise tools!
Answered 06/06/2005 by: francist
Senior Yellow Belt

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