>If the user renames the executable, then the default prompt for the executable will be incorrect but he or she can still browse to it with the old name.
Thanks for pointing me to the right direction). For those who might have problems with source prompt in BA here is solution: 1) Subscribe on BootstrapperApplication.ResolveSource event 2) In event handle execute Engine.SetLocalSource(e.PackageOrContainerId, e.PayloadId, <new_file_location>) (harvest <new_file_location> data somehow). 3) Before handler return, execute e.Result = Result.Retry Note that after that engine will try to resolve source with provided data only once, so it is up to BA to validate if <new_file_location> is a valid source and ask user to reenter path if it is needed. But it is still unclear how patch bundle should handle source missing, if it is launched in Patch relation. There is no way to detect main bundle was launched in silence mode and if patch bundle decides to show dialog for source prompt it may hang some installation script (on PowerShell for instance) rather than just fails. </pre> <font face="arial" size="1" color="#736F6E"> <b>SDL PLC confidential, all rights reserved.</b> If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us.<BR> SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207.<BR> Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. </font> ------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _______________________________________________ WiX-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wix-users
