When you create a bundle with a chain of packages, whether they are run from
a DVD or some other source, they are by default cached in a secure location
on the PC, and the original media is no longer needed by subsequent users.
Why reinvent the wheel? (You can also disable caching on a per package
basis, so your large package could be in your chain, but not copied to the
local PC. See XxxPackage/@Cache)
Also you can stage your packages to a web site, and then the only thing you
need to give to the user (either as a download link or on media) is the
bundle.exe which can be very small if the packages are external to the
bundle. When the bundle runs it only downloads the packages as needed (for
instance when you have platform specific packages). See wix:Update and
MsiPackage/@DownloadUrl. The wix src\Setup\WixBA is an example
implementation in a managed BA, but you can also do it with the WixStdBA.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WiX-Installer-Copy-folder-from-DVD-to-HDD-and-then-run-bootstrapper-from-HDD-folder-tp7599027p7599033.html
Sent from the wix-users mailing list archive at Nabble.com.
------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
