MSI validation and conflicts
Hi,
I am aware of advantages and process MSI valiadation and conflicts.
though it takes lots of time and effort to validate and resolve conflict. Wanted to know if someone has really faces issues because of not resolving ICE and conflicts.
I am aware of the standards and the issues not being followed for that. however my concern is practical issues which have occured as a result of not follwoing standards in MSI
I am aware of advantages and process MSI valiadation and conflicts.
though it takes lots of time and effort to validate and resolve conflict. Wanted to know if someone has really faces issues because of not resolving ICE and conflicts.
I am aware of the standards and the issues not being followed for that. however my concern is practical issues which have occured as a result of not follwoing standards in MSI
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
India_Repackaging
16 years ago
Hi,
I strongly recommend to solve most ICE errors and warnings. Though in most cases they will not affect the application functionality but you may not be able to reap all benefits provided by Windows Installer,
Hence I dont not think most application packagers would advice to keep many ICE errors and warnings unsolved, except when they do not affect the functionality of the application.
Conflict Resolution: I think all conflicts between applications (ones already installed or ones that would be installed) should be analyzed properly. This proves very important when you have to check Desktop integrity i.e. co-existance of applications that are sharing resources between them and file version conflicts, etc can be dealt with.
I strongly recommend to solve most ICE errors and warnings. Though in most cases they will not affect the application functionality but you may not be able to reap all benefits provided by Windows Installer,
Hence I dont not think most application packagers would advice to keep many ICE errors and warnings unsolved, except when they do not affect the functionality of the application.
Conflict Resolution: I think all conflicts between applications (ones already installed or ones that would be installed) should be analyzed properly. This proves very important when you have to check Desktop integrity i.e. co-existance of applications that are sharing resources between them and file version conflicts, etc can be dealt with.
Posted by:
anonymous_9363
16 years ago
Ever validated a Microsoft MSI? Frankly, some errors can never be satisfactorily resolved. Often, fixing one will produce another. Ultimately, this comes down to a judgement call between the packager, QA (if any) and the Systems/Desktop people (if any).
Posted by:
dm1
16 years ago
I'd tend to side with VBScab on this.
The irony of Microsoft MSIs riddled with errors and warnings is well documented.
Of course for repackaged MSIs from legacy setups you should try and solve them all, but for Vendor MSIs I think the general industry modus operandi is to leave as is as long as they don't effect application functionality.
The irony of Microsoft MSIs riddled with errors and warnings is well documented.
Of course for repackaged MSIs from legacy setups you should try and solve them all, but for Vendor MSIs I think the general industry modus operandi is to leave as is as long as they don't effect application functionality.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
