Is it best practice to create a windows installer package for all apps before creating an AppV version?
I'm just working on a packaging workflow and am thinking it would make more sense to attempt the creation of an AppV package and if unsuccessful, create an MSI.
However, I'm wondering if it is best practice to create a windows installer package (MSI/MST) for apps before creating an AppV version?
Your input would be appreciated.
-
Thanks everyone for your comments, they have been very helpful. Many thanks. - Waynepfisher 7 years ago
Answers (4)
Naye.
I think your best options is to create the App-V package, then failing that create the MSI. I say this because its normally easier to configure whilst installing with installer GUI, than trying to do a silent install with an MST. Don't forget you need to do App-V remediation as well, you don't want to MSI package and App-V package - its like asking to do twice as much work for one package (;
Well my 2p anyway.
First of all I'm creating AppV package + remediation in case of any issues. If it does not work then I'm creating MSI (as customer needs requested App :) + conversion to AppV (just to check, because usually if vendor captured to AppV does not work, then catured MSI converted to AppV will not work too ;)
If you have the 'right' tools you can snapshot once and build into multiple outputs.
Installshield can do it with what they used to call the Virt Pack, and Caphyon Advanced Installer can do it.
Something to consider if you have those tools available.
Dunnpy
