Roger Yen wrote: > Actually this is not what I'm looking for. Since I need to be able to > refer to the jar file when I call a custom action during installation, > before the actual installation of files, what I want is to be able to > get the path to the jar component "in the backup files", not the target > path.
The files don't exist until they're installed. You could write a custom action to extract them if they're in the Binary table but there's no support to get at files embedded in CABs embedded in an MSI without going through installation. Why does the custom action have to run before the files are installed? -- sig://boB http://joyofsetup.com/ ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
