/build/static/layout/Breadcrumb_cap_w.png

Tool to identify commonalities between MSIs

Hi,

I'm trying to troubleshoot a problem where one program stops working when two others are added to the mix. Is there a tool which will indentify commonalities between two MSIs? Most of the MSI comparison tools seem to be targetted at two MSIs which will have some differences. My MSIs are completely different, but I need to find what they have in common.

cheers
Mike

0 Comments   [ + ] Show comments

Answers (8)

Posted by: AngelD 17 years ago
Red Belt
0
Don't know what tool you're using for packaging but with Wise Package Studio you could use Conflict Manager to find resources conflicting with each other in different packages.
Posted by: meastaugh1 17 years ago
Senior Purple Belt
0
Hi,

I'm using WPS Standard, can't afford pro as we're a school. Is there anything that could do this?

Thanks
Mike
Posted by: AngelD 17 years ago
Red Belt
0
Don't think there is in the Standard edition, will see if I can think of something
Posted by: AngelD 17 years ago
Red Belt
0
How about converting the MSI files to xml and then use "Merge for Windows" from araxis to compare the xml files. You can download a "Free trial: download fully-functional 30-day evaluation"

You can also use WinMerge, which is free
Posted by: turbokitty 17 years ago
6th Degree Black Belt
0
You could just download a trial of the full Wise Suite and give Conflict Manager a go.
Posted by: AngelD 17 years ago
Red Belt
0
I'm not sure you will have access to the Conflict Manager in evaluation mode, but not sure either so.
Posted by: MSIMaker 17 years ago
2nd Degree Black Belt
0
ORIGINAL: AngelD

I'm not sure you will have access to the Conflict Manager in evaluation mode, but not sure either so.


From memory the Eval version lets you import 5 apps into it and its fully functional.
Posted by: AngelD 17 years ago
Red Belt
0
It was so long ago I used evalutation version so good feedback there Jim.

meastaugh1: 5 packages will be sufficient for you to be able to conflict your packages to leed you in the right direction on whats conflicting.
Think you're after either a registry or dll conflict.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ