Hello all

Concerns: Windows Package Studio 6.0 Pro Edition using share point config.

Everytime I perform a snapshot of an installation, at the end Wise collects all files and performs some kind of 'compile' and saves the WSI file in the project's folder.
Afterwards I have to open Windows Installer Editor to actually compile the MSI file (compress files into MSI file).
I find this really annoying because I'm used to, like with SMS Installer, compile directly in an EXE or MSI file.
Am I doing something wrong here? I've checked all possible options in the Share Point configuration and such...

edit:
Actually what I want as end-result is just the compiled MSI file in the project's folder, nothing more, nothing less.... is this possible??
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
There isn't anyway around this that I know of. I think that with EXE's it compiles the final application after the capture but my experience with MSI's has been the same as yours.
Answered 02/06/2006 by: yarborg
Blue Belt

Please log in to comment
0
Yes this is possible, can't remember exactly where you set it - it's a while since I seup WPS from scratch.

Think it's defined in the "Windows Application" wise template somewhere.. will have a look tomorrow if I get chance.

Regards,
Rob.
Answered 02/06/2006 by: MSIPackager
Third Degree Black Belt

Please log in to comment
0
aha... thanks for the tip MSIPackager ...

I guess you mean the 'Don't update or recompress files when saving (.MSI only)' option in the 'Product Details' view within the Windows Application.MSI template file ... right?
Answered 02/06/2006 by: renio
Senior Yellow Belt

Please log in to comment
0
Nope, that's not it. In fact it's not in the Windows Application template at all...! In order to capture directly to an MSI I belive you have to configure a custom command line for the setup capture tool (which you do in the process template setup) - there are a few examples there already which are all setup for [FileName].wsi

You can either modify and use one of the examples or create a new command line - ensuring you are using the /tgt= switch (e.g. /tgt="[ProjectDir]\[FileName].msi). Now, when you create a new project and run the setup capture tool from your process it will compile an MSI immediately, rather than an WSI first.

The Windows Application template I mentioned is where you can specify other defaults - such as Add/Remove Programs and Media options.

Hope it helps,
Rob.
Answered 02/07/2006 by: MSIPackager
Third Degree Black Belt

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