Re: [WiX-users] harvesting COM information using heat.exe results in HEAT5150

2012-05-26 Thread Brian C
Hit send too early For us, we compared the heat extraction with the .reg results from using RegSpy for our 64 bit dlls.   Everything was the same except the source path, so the script just copies the .wxs generated by heat and replaces the source path with the 64 bit location.   Brian

Re: [WiX-users] Finding Related Products

2012-05-26 Thread Rob Mensching
AppSearch? On Fri, May 25, 2012 at 8:58 AM, Rob Hamflett rob_hamfl...@sn.scee.netwrote: Is there a way to check for pre-existing products other than via FindRelatedProducts? The problem I have is that regardless of the operation (install/repair/remove) I need to discover if some of our

Re: [WiX-users] Custom MBA, adding extra metadata to the Bootstrapper Application Data

2012-05-26 Thread Rob Mensching
You just add rows to a table that has BootstrapperApplicationData=yes. The Binder will translate all those rows into the BootstrapperapplicationData.xml in the Bundle. On Thu, May 24, 2012 at 2:12 PM, Hoover, Jacob jacob.hoo...@greenheck.comwrote: Has anyone tried with success to allow dynamic

Re: [WiX-users] Burn managed UI - how to cancel and rollback?

2012-05-26 Thread Rob Mensching
Set the args.Result to cancel on a callback and the engine will stop progressing as soon as possible and rollback if appropriate. On Fri, May 25, 2012 at 1:40 PM, Nick Ramirez nickra...@hotmail.com wrote: So, assuming I put a cancel button onto my managed bootstrapper application UI, can

Re: [WiX-users] Burn SQL Server 2008 Uninstall not being called.

2012-05-26 Thread Rob Mensching
Your ExePackage needs a DetectCondition attribute to be detected. On Fri, May 25, 2012 at 10:53 AM, Benjamin Bennett benbenn...@gmail.comwrote: Nope that wasn't it . Nothing in the SQL server logs. Burn is checking if it is installed somehow and determining that it isn't installed. On Fri,

Re: [WiX-users] Custom action fails with error code

2012-05-26 Thread Rob Mensching
Looks like your custom action is no longer returning ERROR_SUCCESS. CustomAction UpdateConfig returned actual error code -2146232576 That or maybe the custom action is crashing and Windows Installer is just letting you know. You might try MsiBreak to debug. On Fri, May 25, 2012 at 11:57 AM,

[WiX-users] Burn: DetectCondition run a local executable right before starting an ExePackage

2012-05-26 Thread chefkoch
Hi, I am starting to use Burn as a bootstrapper around our product's msi and a few dependencies. I can at some DetectConditions for checking whether the dependency is already present on the pc. I started with a Util:RegistrySearch, which is working fine. I would like to add another variable

Re: [WiX-users] Burn: DetectCondition run a local executable right before starting an ExePackage

2012-05-26 Thread Rob Mensching
1. Not supported today but seems like a reasonable thing to request. 2. Burn only references packages that are carried as part of itself. On Sat, May 26, 2012 at 11:01 AM, chefkoch chefk...@team-mediaportal.comwrote: Hi, I am starting to use Burn as a bootstrapper around our product's msi

Re: [WiX-users] Burn: DetectCondition run a local executable right before starting an ExePackage

2012-05-26 Thread chefkoch
Hi Rob, thanks for support. Regarding the Min/MaxSize attributes, I created a ticket1. I created a tickethttps://sourceforge.net/tracker/?func=detailaid=3529770group_id=105970atid=642714 for it. The command which needs to be started before the ExePackage, uninstalls an old version of the