Quick question. After repackaging an application (or I guess creating a new application from scratch), what do people consider to be best practice in regards to on going modifications? Do people modify the .msi file directly, or do they modify the .ism (or whatever the configuration file other programs use) and rebuild a fresh MSI each time?
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


That depends on the environment, surely? Most clients I've worked for ask that the source file (be that WSI, ISM, whatever) always be changed and compiled. Some of the more enlightened ones use source/version control. That way, everyone knows which is the authoritative source. Otherwise you end up with Packager X altering the MSI but then Packager Y altering the WSI and missing the changes in the MSI.
Answered 07/10/2007 by: VBScab
Red Belt

Please log in to comment
Thanks VBScab. That was my thoughts as well, but I just wanted to see if that is what others also did. If anyone else has an opinion as well, I'd be interested in hearing. I'm trying to create a policy for my work regarding whether the ISM or MSI file is what should be modified. As you say, you're going to run into problems if the packagers aren't working on a standard file format.
Answered 07/10/2007 by: brettski
Purple Belt

Please log in to comment