What is your view on the use of conflict management
Currently we are using Wise Package studio and we do conflict management on msi's . This is pretty time-consuming. Do you use conflict management. do you think it is worth the effort ?
0 Comments
[ + ] Show comments
Answers (5)
Please log in to answer
Posted by:
jmcfadyen
15 years ago
if you never EVER plan to uninstall anything. Be that upgrade or whatever means of uninstall then conflict management is limited in its uses. However I have rarely ever seen a site that can claim they will never uninstall anything as such I would say CMDB is a highly valuable solution.
conflict managers Core purpose is to protect your system from breakages during uninstall however in saying that
Conflict management does one thing which is potentially very important which many people overlook.
That item is it ensures applications are actually deployed properly in specific instances. These instances are limited in real world application but equally important.
Component structure is extremely important in MSI creation, something that Installshield has 0 visability off as the component structure in Installshield captured applications is appalling.
The specific item I refer to is this.
When an application has similar components such as
Application A
Component A (Directory A)
FileA.exe = keypath
and another application has similar
Application B
Component A (Directory A)
FileA.exe = keypath
FileA.junk
You run into a potentially dangerous situation which is.
If application B goes down first, there is no issue.
If application A goes down first then FileA.junk will not get delivered as its component state will be set to installed and the components clients will just be updated to include application B
If FileA.junk was important then your screwed. If not its not so bad.
A well configured conflict manager would resolve this. Taking this into consideration go back and have a look at the component structure of an installshield application.
conflict managers Core purpose is to protect your system from breakages during uninstall however in saying that
Conflict management does one thing which is potentially very important which many people overlook.
That item is it ensures applications are actually deployed properly in specific instances. These instances are limited in real world application but equally important.
Component structure is extremely important in MSI creation, something that Installshield has 0 visability off as the component structure in Installshield captured applications is appalling.
The specific item I refer to is this.
When an application has similar components such as
Application A
Component A (Directory A)
FileA.exe = keypath
and another application has similar
Application B
Component A (Directory A)
FileA.exe = keypath
FileA.junk
You run into a potentially dangerous situation which is.
If application B goes down first, there is no issue.
If application A goes down first then FileA.junk will not get delivered as its component state will be set to installed and the components clients will just be updated to include application B
If FileA.junk was important then your screwed. If not its not so bad.
A well configured conflict manager would resolve this. Taking this into consideration go back and have a look at the component structure of an installshield application.
Posted by:
speedmovin
15 years ago
Posted by:
jmcfadyen
15 years ago
component rules are a complex world.
way too much to explain in this post but the general idea is this
if files are deploy to same locations component guids should be matched regardless of version assuming the same manufacturer
the versioning rules you mention are a window installer feature as opposed to wininstall which is just the editor. I have gone into much more detail on component rules / conflict management on my blog if you get bored.
way too much to explain in this post but the general idea is this
if files are deploy to same locations component guids should be matched regardless of version assuming the same manufacturer
the versioning rules you mention are a window installer feature as opposed to wininstall which is just the editor. I have gone into much more detail on component rules / conflict management on my blog if you get bored.
Posted by:
speedmovin
15 years ago
Posted by:
anonymous_9363
15 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.