straubtm
asked on
How best to distribute Flashplayer (via MSI) with my Windows app
I have been granted a license to distribute the Adobe Flash Player 10 with my windows app. However, I am looking for the cleanest and most efficient way to distribute it. The installer is offered in both EXE and MSI formats (and I could also direct them to the web to install).
I've read that one MSI cannot call another MSI and that a bootstrapper is required for VS 2005 setup projects. That seems like a sloppy end-user experience. The exe could be launched as a process, but I'm not sure how best to code that into the setup and wait until the process ends.
Does anyone have experience incorporating the Flashplayer distribution with their Windows Apps? And if so, do you have any suggestions for the best user experience?
I've read that one MSI cannot call another MSI and that a bootstrapper is required for VS 2005 setup projects. That seems like a sloppy end-user experience. The exe could be launched as a process, but I'm not sure how best to code that into the setup and wait until the process ends.
Does anyone have experience incorporating the Flashplayer distribution with their Windows Apps? And if so, do you have any suggestions for the best user experience?
ASKER
I was hoping to run the msi silently using something like msiexec and the /qn command line parameter... however, I cannot run that from a CustomAction within another msi. So, It appears I am stuck using the Bootstrapper Manifest Generator and a package manifest for the flash msi. This will run, but will not silently.
Are there any other options?
Are there any other options?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
That said, I don't quite understand your problem. You've got MSI from them, which supposedly would install the product so why "MSI cannot call another MSI"? why the need to call one MSI from another?