I am trying to convert few WSE\EXE files created by Wise Script Package Editor into MSI format.

Has someone already tried this?

1) How much is the reliability of this tool in creating msi packages from legacy applications.[/align]2) What are the potential risks or downsides associated with this tool.[/align]3) Exactly which type of applications can this tool be used for.[/align] [/align]It is my observation that :-[/align] [/align]1) Wise script executables containing custom actions fail to convert properly into msi using this tool.[/align]2) Executables (wise script or any other) containing ODBC settings fail to convert properly into msi.[/align]3) Executables (wise script or any other) containing services fail to convert properly into msi.[/align]4) Executables (wise script or any other) containing file associations fail to convert properly into msi. The associations are missed out during conversion.[/align]
0 Comments   [ + ] Show Comments

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.

Answers

0
ORIGINAL: Lillude
1) How much is the reliability of this tool in creating msi packages from legacy applications.
Which tool would that be? We could guess at Wise Package Studio but then comes the next question: which version?
Answered 07/14/2008 by: VBScab
Red Belt

Please log in to comment
0
tools is Legacy Setup Conversion...and it is available with 5.5, 6, 7 versions of wise (might be various other versions as well, I have just used these three)
Answered 07/14/2008 by: Lillude
Senior Purple Belt

Please log in to comment
0
OK, so Wise Package Studio.

Never bothered, given a) Wise's/Altiris' track record and b) the potential unknown quantity of who packaged it last into the WSE.. I just capture the EXE. That way, I end up with a known quantity.
Answered 07/14/2008 by: VBScab
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity