Conflict Explorer 2009 provides the following powerful feature set:

• Conflict display for all imported software packages
  Once a software package has been imported and scanned, the potential conflicts between this newly-imported software package and any other selected software packages are displayed. Conflict display persists until all conflicts are corrected.
    
• User-managed and automatic conflict resolution within separate or existing MSTs
  Corrections are always performed in a single transform. This practice ensures that the correction is easily auditable. Accordingly, a simple deletion process makes it just as easy to revoke corrections. Automatic corrections are carried out with a single click.
   
• Ability to selectively resolve individual conflicts, according to user settings
  Packagers are also able to correct conflicts individually, according to their own rule sets. 
   
• Can be used without problems even on manufacturer MSIs
  without the risk of negative consequences. (Not just for custom repackaged packages)
   
• Comparison of various resources as 1:n and not just 1:1
  Data about files, Registry, etc., is supplemented by SelfReg information, which is then compared to all SelfReg and registry values.
   
• Packagefamily excludes
  Option of hiding conflicts from packages on a PackageFamily exclude list with a single mouse click. For example, if conflicts between StarOffice and Microsoft Office should not be displayed (perhaps because we know that in certain circumstances these applications are never installed onto clients together), then it is possible to use a PackageFamily exclude in order to hide all of their reciprocal conflicts (see also the use of groups). Another example would be where two software products are technically incompatible and this scenario is managed via software distribution. Here also, there is no sense in packages displaying their reciprocal conflicts to us – a PackageFamily exclude is again a sufficient technique.
  
   
• Conflikt excludes
  Each and every conflict can be hidden or given its own individual annotation. Where necessary, all of these hidden conflicts can be listed and then re-displayed on a case-by-case basis.
  
   
• Real conflicts
  (E.g. a file contained in one package compared to a file of the same name in another package will not lead to a conflict if such files are identified as being located in different directories)
   
• Data integrity
  Data shown is 100% correct!
   
• Usability benefits
  Sorting of conflicts, column swapping, direct access to individual data items (copy to clipboard), etc., and much more. Simple user interface and layout, similar to Windows Explorer.
  
   
• Categorised and extended display of conflicts
  Value Conflicts, Standard Conflicts.
   
• Powerful, robust import system
  No MSIs have yet been identified that could not be imported.
  
   
• Resolution of Windows Installer properties
  The majority of properties will be resolved, as long as they are not the result of custom actions. AppSearch properties are identified for each package, and also entered as clear text in the database.
   
• MST support during import
  Support for one, multiple or variable MSTs during import.
   
• Display usability features
  Instant visual notification (icon) when browsing packages in the tree view for conflict packages and packages that have been corrected automatically. Behaviour of this feature can be controlled precisely by user settings.
  
   
• Support for the action state!
  Parsing and display of the ActionState for a component, plus accounting for the ActionState during automatic conflict resolution! 
  
   
• Conflicts with the operating system
  Conflicts are not only identified between software packages, but can also be displayed between software packages and the operating system itself. This permits the creation of software packages free of any operating system conflicts.
   
• Configurable display of conflicts
  Conflict display in the list view is user-configurable: "display all keys/files only once", "display only installed components", etc. 
   
• Search
  Search through a variety of content from conflicts (F3)
  
   
• Handy display of additional information
  Import date, number of conflicts before/after an operation, etc.
   
• A number of practical "little helpers"
  For simple and direct opening of the underlying MSI file using a specified program (e.g. Orca), for rapid navigation through the MSI file system (Explorer), etc. Accounting for a number of different file shares (development/test/production).
   
• Recognition of dependencies via conflicts
  By using Conflict Explorer, dependencies present as self-contained packages can also be visualised. Such as the scenario where a repackaged package has third-party components still contained in the snapshot that would otherwise be present as self-contained products, for example.
   
• Optional integration into Wise Package Studio
  Conflict Explorer is a self-contained product and can be deployed together with any authoring suite, or even without such an authoring suite being present. Nonetheless, a number of command line switches make it easy to embed the product directly into projects from Wise Package Studio.
   
• Multi-client capable and/or suitable for use in groups
  Within a company, one often supports a number of different sets of clients or develops for a number of different customers – such as German, French or English clients. Some of the software will be the same and some will vary between these groups. Since a variety of groups can be used freely, these and other kinds of mappings are easy to implement. Packages can be moved immediately once imported or at a later date, copied from one group to another, groups can be renamed, etc. Such operations are quick to complete and do not cause any delays. Conflicts will be displayed only for packages that have a specific group membership. 
  
   
• No unnecessary changes
  Keeping to the basic rule: "Fix as much as is needed, but as little as possible!"

kw