Skip conflict management in msi packaging?

What is you view on skipping conflict management in the msi repackaging process. Is it a risk worth taking or can it cause big problems ?
Who is Participating?
Rory de LeurConnect With a Mentor Consultant End-User ComputingCommented:
I work at a company maintaining over 900 msi based applications.. we use Wise and have used the conflict database once when we hit an error..

We skip it in the process, it takes up to much time.
Vadim RappCommented:
conflict with what? do you have some specific product in mind?
Vadim RappConnect With a Mentor Commented:
Actually, you see the risk yourself whenever you actually run conflict checker. If it finds conflicts, you see what they are. if you neglect fixing them, then obviously you can drop the checking. But the feature is there in order to save you time on troubleshooting consequences of these conflicts, such as installation A overwriting a file belonging to B; uninstalling A removing a file also used by B; A upgrading the DLL used by B, although it was not tested if it's fully compatible and new version won't break B; and so forth - chances are, troubleshooting of these things will eat much more time than checking the conflicts.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.