Hello all

I'm a regular visitor of the appdeploy.com site and its forums, but just now created an account to post my question here...

We're starting on a new project at a new customer site and discussions arised about repackaging versus usage of the original silent setup (if it exists). If we'd go for repackaging it would be done with Wise Package Studio 6 taking the 'advantages' of the conflict management features.
The customer pushes us to apply just one rule: repackage everything in MSI and that little percentage of applications that fail to be repackage...use - if any - silent setup from the vendor.
Personally we've always tried to figure out the vendor silent setup and if that failed we'd go for repackaging.
So my question is: would you try to repackage everything in MSI?

And another question: What SQL server version (including service pack) does Wise Package Studio 6 need? What other requirements do we need for the implementation of Wise?


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


hi renio,

basically there are (self written) rules that apply as to wether an application needs to be repackaged to MSI formats or not.. here are several types of package we normally package to MSI's..
EXE that is not a launcher for an MSI, Legacy application package setup.exe, Legacy applications without setup.exe and In-House developed applications.
For vendor supplied MSI's wrapped in EXE, the msi's should be extracted and all customisations should be via Transforms (if in case where the application cannot run outside the EXE then installation should be via command line or a response file should be created). Same as vendor supplied MSI's not using setup.exe's.. all customisations via MST's

i'm using a SQL server 2000 SP3

Answered 11/22/2005 by: rikx2
Purple Belt

Please log in to comment