Re: [WiX-users] Only one Registry Entry gets deleted while Repair

The three components are: Not Installed Not Installed Not Installed First and last component remains the same but middle one gets flushed. I have this following log: MSI (s) (80:C8) [17:42:54:941]: Executing op: CacheSizeFlush(,) MSI (s) (80:C8) [17:42:54:941]: Executing op:

Re: [WiX-users] Only one Registry Entry gets deleted while Repair

Would it be possible to provide the 3 components which describe the 3 values in question? In addition, since I assume you are rewriting these values during a repair it would be interesting to see how you are populating the property values. Have you searched the log files after re-invoking the in

Re: [WiX-users] Light.exe error: Value cannot be null

Hi, 1) I tried that clean/rebuild before posting, and it didn't make a difference. 2) The only info I get is what I wrote in my first message: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/file/n7578853/screen.png I really would like to know which value can't be null. There

Re: [WiX-users] Only one Registry Entry gets deleted while Repair

Ok to test Repair I manually delete some files and rerun the installer. It puts back all the file at the same places again (great, I guess). But even if i don't delete or touch any files and just simply runs the repair. Same thing happens. the registry gets deleted but other two remains the same a

Re: [WiX-users] Only one Registry Entry gets deleted while Repair

>From msiexec /?, Repair Options /f[p|e|c|m|s|o|d|a|u|v] Repairs a product p - only if file is missing o - if file is missing or an older version is installed (default) e - if file is missing or an equal or older version is

Re: [WiX-users] Only one Registry Entry gets deleted while Repair

I have seen log for those valus and they are: MSI (s) (80:C8) [17:42:53:519]: PROPERTY CHANGE: Adding REINSTALLMODE property. Its value is 'ecmus'. MSI (s) (80:C8) [17:42:53:519]: PROPERTY CHANGE: Adding SECONDSEQUENCE property. Its value is '1'. MSI (s) (80:C8) [17:42:53:519]: PROPERTY CHANGE: Add

Re: [WiX-users] Only one Registry Entry gets deleted while Repair

Hmm, I'd bet that if you compare the REINSTALL and REINSTALLMODE properties of the log files from both would show a difference. I'm a bit confused as to why you are expecting key path (registry) entries to be deleted. If the key path is saying the component is there and a repair happens and

[WiX-users] Only one Registry Entry gets deleted while Repair

I am seeing this strange behavior of my installer while performing Repair. When I do Right-click -> Repair, things happens great. I get back my missing (deleted) files. and also custom action preforms great. But when I double-click the installer and perform repair via Maintenance Mode, things happe

Re: [WiX-users] Burn and util:ProductSearch, Result="state"

https://sourceforge.net/tracker/?func=detail&aid=3535318&group_id=105970&atid=642714 Think that would be done right... -Original Message- From: Bob Arnson [mailto:b...@joyofsetup.com] Sent: Thursday, June 14, 2012 1:46 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Burn

[WiX-users] ServiceDependency, using a foreign key

The docs for the ServiceDependency Element say: Id: The value of this attribute should be one of the following: 1. The name (not the display name) of a previously installed service. *2. A foreign key referring to another ServiceInstall/@Id.* 3. A group of services (in which case the Group attribu

[WiX-users] Bootstrapper UpgradeCode

What's the UpgradeCode for on Bundles? I understand that in Products it searches for any existing products with the same upgrade code and removes them when installing the new one. I don't see how having an UpgradeCode on the bootstrapper is relevant, since it doesn't get installed. In other word

Re: [WiX-users] Should you install 32-bit and 64-bit versions os the same application?

Hi Gareth, I don't currently use the DuplicateFile table because my 32-bit components and 64-bit components are distinct - mainly because we provide 32-bit support for our APIs but the full product is native 64-bit on a 64-bit O/S i.e. the user runs the 64-bit product, but can access 32-bit API

Re: [WiX-users] BootstrapperApplication Run

I thought the message pump might be the reason. I am targeting .Net 2.0 so there isn't a Dispatcher.Run() so I'll have to find alternative. Thanks Neil -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: 14 June 2012 16:39 To: General discussion for Windows Inst

Re: [WiX-users] v3.6.3013.0

On 14-Jun-12 07:43, Neil Sleightholm wrote: > Are there any changes from build 3.6.3005.0 to 3.6.3013.0 – the history entry > for this release is empty. You want v3.6.3014.0, out now. -- sig://boB http://joyofsetup.com/

Re: [WiX-users] Light.exe error: Value cannot be null

1. Be sure to rebuild everything. Left over .wixobj files can create very strange behaviors. 2. Was a call stack provided? Can you provide more information about the error? On Tue, Jun 12, 2012 at 8:49 AM, Miss Parker wrote: > Hi, > > I upgraded to Wix Toolset RC today, and suddenly some MsiPack

Re: [WiX-users] burn - UninstallCommand

Burn in WiX v3.6 does not support running executables on disk. Only the executable that came with the Bundle can be executed today. On Wed, Jun 13, 2012 at 10:50 AM, wrote: > Hi, > > I am starting to evaluate burn. > > I am trying to create a bundle that includes a 3rd party installer (not > muc

Re: [WiX-users] Conditions for Install, Uninstall, Repair

ok i got this Remove="ALL" works great. On Thu, Jun 14, 2012 at 2:19 PM, Ravi Raj wrote: > I have checked that InstallMode = "Repair" or InstallMode = "Remove" is > not working at all. > > > On Thu, Jun 14, 2012 at 12:56 PM, Ravi Raj wrote: > >> I am using these conditions but they are behaving s

Re: [WiX-users] Should you install 32-bit and 64-bit versions os the same application?

Yes, that's the approach my team and I concluded to last night... to stop having a 32-bit package for the 32-bit components and a 64-bit package for the 64-bit components. Leave the 32-bit components in the 32-bit package, but stop it installing on 64-bit and duplicate it's core elements in the 64-

Re: [WiX-users] Conditions for Install, Uninstall, Repair

I have checked that InstallMode = "Repair" or InstallMode = "Remove" is not working at all. On Thu, Jun 14, 2012 at 12:56 PM, Ravi Raj wrote: > I am using these conditions but they are behaving strangly: > > Action="CA_SetProperty_MACHINENAME" After="CostFinalize">NOT > Installed After="CA_SetP

[WiX-users] Conditions for Install, Uninstall, Repair

I am using these conditions but they are behaving strangly: NOT InstalledNOT Installed (NOT Installed) OR (UPGRADINGPRODUCTCODE) OR NOT(REMOVE = "ALL")(NOT Installed) OR (UPGRADINGPRODUCTCODE) OR NOT(REMOVE = "ALL") OR (Installed AND (InstallMode = "Repair")) Installed AND (InstallMode = "Repair

[WiX-users] v3.6.3013.0

Are there any changes from build 3.6.3005.0 to 3.6.3013.0 - the history entry for this release is empty. Neil Neil Sleightholm X2 Systems Limited n...@x2systems.com -- Live Security Virtual Co

Re: [WiX-users] Should you install 32-bit and 64-bit versions os the same application?

This option is, theoretically, possible and readily available to you. This depends on the needs of your program though. Doing this just so you can have it is not the right reason, but if there is an actual need for it the go ahead. Some things that you will have to watch out for, however, would

Re: [WiX-users] Light.exe error: Value cannot be null

On 12-Jun-12 11:49, Miss Parker wrote: > I upgraded to Wix Toolset RC today, and suddenly some MsiPackage elements in > my bundle generated an error: "Value cannot be null" (Light.exe) There are Please post the stack trace. -- sig://boB http://joyofsetup.com/ -

Re: [WiX-users] WiX 3.6 Upgrade Leaves Files in Cache (v3.6.2520.0 to v3.6.2527.0)

On 12-Jun-12 00:39, Kannan24 wrote: > How to disable the respective MSI feature from windows form? Handle OnPlanMsiFeature. > I mean the "Class library" is like WixBA.dll. I need to set the MSI property > values from WixBA.dll. IBootstrapperEngine::SetVariableString. -- sig://boB http://joyofset

Re: [WiX-users] Burn Failure 0x8007051b

On 12-Jun-12 16:13, Neil Sleightholm wrote: > Yes - Variable: WixBundleElevated = 1 > > Could it be that UAC is disabled therefore it is elevated but it actually > needs to be an administrator as well? Right and Burn has logic to handle that state (same as old-school standard user on XP/2003). Bu

Re: [WiX-users] Windows Installer 3.1 or 4.5 for XP?

It is our practice to require at Windows Installer 4.5 on XP and Windows Server 2003. It has a pretty widespread impact on the client-facing stuff--many of our clients still use XP. Sales applies pressure to not require SP's, let alone Windows Installer 4.5, but the security implications alone

Re: [WiX-users] Burn and util:ProductSearch, Result="state"

On 14-Jun-12 14:30, Hoover, Jacob wrote: > [2DB4:40F8][2012-06-14T12:57:17]: Error 0x80070648: Failed to get product > info. Please file a bug; I'll make sure there's a test if there isn't one already. -- sig://boB http://joyofsetup.com/ -

[WiX-users] Burn and util:ProductSearch, Result="state"

Hmm, I can't believe this would make it through some basic testing but here goes... I am attempting to detect the state of a product (VC 2005 Runtime) using the following snippet. When I use a result other than state, then the search functions as expected, however if I use state it

Re: [WiX-users] Extracting embedded packages from the standard bootstrapper

dark can be used as described. However, my customers don't have WiX installed and may not have .Net - I am under the impression that dark uses .Net. What I'm looking for is to give them a single file. If they want access to the embedded packages I would like to be able to tell them to just run the

Re: [WiX-users] Windows Installer 3.1 or 4.5 for XP?

Thanks for letting me know that WiX will work well with Windows Installer 3.1 and there are no current plans to change this. Now all I have to decide is whether I need features from Windows Installer 4.5 for my custom actions. Would you care to speculate if you ever plan to require a newer version

Re: [WiX-users] Burn Failure 0x8007051b

The solution for this was to add a bal:Condition to my bundle: Privileged If the user is not an admin and UAC is off then the burn cannot elevate and therefore the install needs to be blocked (like you would with an MSI). Neil -Original Message- From: Neil Sleightholm [mailt

[WiX-users] using WixUI_Advanced

I'm trying to use the FeaturesDlg in WixUI_Advanced but I cannot get the Wix tools (called through Visual Studio) to recognize FeaturesDlg, the xml tag. I've tried adding a UIRef tag with the Id="WixUI_Advanced" as suggested in the help file, but it still is not recognized. I've also tried nesting

Re: [WiX-users] BootstrapperApplication Run

The WixBA.Run() method calls the Dispatcher.Run(). The dispatcher is the message pump for the UI. Without the message pump, the WPF UI won't do respond (even to redraws ). So, for the WixBA, it needs to run this way. If you do not have a UI then you technically can do everything via the callbacks.

Re: [WiX-users] light.exe error when merging VC100 merge modules for both x86 and x64

On 13-Jun-12 06:22, Gareth wrote: > Yes it can. You can also use a hammer to tighten a screw, but it's not recommended. The VC9 and VC10 CRTs are very different (VC9 goes into the Fusion GAC; VC10 doesn't) so it's no surprise they behave differently. -- sig://boB http://joyofsetup.com/ ---

Re: [WiX-users] burn - UninstallCommand

On 13-Jun-12 13:50, chro...@comcast.net wrote: > I am trying to create a bundle that includes a 3rd party installer (not much > control over it). It is an exe, so I created an ExePackage. Now, to uninstall > that package, it seems like I need to run the unwise.exe that the installer > put in the

Re: [WiX-users] WiX CustomBA Debuging

Just working on a managed bootstrapper myself... Using Debugger.Break() I can successfully attach Visual Studio to the bootstrapper application. No problem stepping through the code from there. Kind regards, Henning > -Original Message- > From: Rob Mensching [mailto:r...@robmensching.

Re: [WiX-users] Extracting embedded packages from the standard bootstrapper

dark.exe is used to decompile Bundles back to their individual parts. On Wed, Jun 13, 2012 at 2:13 PM, Don Walker wrote: > If I do need to provide my customers access to the embedded msi files from > a bootstrapper I would like to be able to extract them instead of needing > to provide them separ

Re: [WiX-users] Burn: Exe package can't find payload file that's not a dll.

Please file a bug to track the need to set the working directory to the cache folder before launching executables. Fragile code creating more work for us. On Wed, Jun 13, 2012 at 10:30 AM, wrote: > I have the same issue. Allowing us to change directory would be good. Or > at least have a prope

Re: [WiX-users] light.exe error when merging VC100 merge modules for both x86 and x64

Most likely the VC100 Merge Module changed and no longer support doing what was done in VC90. We didn't purposely change the WiX toolset to block it. If you run with the -notidy switch to light (I think that's the name) there should be a log file somewhere under %TEMP% that will show the mergemod.

Re: [WiX-users] Install location for Wix 3.6

Not today. On Wed, Jun 13, 2012 at 4:26 AM, Subbiah Ganesan wrote: > Hi, > > Is there a way to specify install location for Wix3.6. Currently i am > using WiX Toolset v3.6.2221.0. It is getting installed under "C:\Program > Files (x86)\Windows Installer XML v3.6". I want to change this while > in

Re: [WiX-users] Windows Installer 3.1 or 4.5 for XP?

The straight WiX toolset should never require anything more than MSI v1. However, the Windows Installer really isn't "good" until MSI v3.1 and much functionality doesn't work well until you have MSI v3.1. MSI v4.5 isn't well distributed so we only take advantage of features there opportunistically

Re: [WiX-users] Wix Toolset installation fails, a bit urgent!

Working for me now. Might have been a temporary network glitch. On Tue, Jun 12, 2012 at 11:16 PM, Miss Parker wrote: > Hi, > > I had a few problems with the new Wix Toolset RC, so I decided to reinstall > it, but it keeps failing. I tried to copy paste the links into my browser > and got Network

Re: [WiX-users] WiX CustomBA Debuging

1. No. 2. As long as the name of the .pdb file does not change, the debugger will be able to find the .pdb if you put it in your symbol path. Try right clicking on your BA .dll and there should be an option to modify the debugging symbol paths. You can also find it in Tools -> Options. On Mon, Ju

[WiX-users] v3.6.3013.0

Are there any changes from build 3.6.3005.0 to 3.6.3013.0 – the history entry for this release is empty. Neil Neil Sleightholm X2 Systems Limited n...@x2systems.com -- Live Security Virtual Co

Re: [WiX-users] Burn Bootstrapper and SQL Server 2008 R2 Express

I have just remembered burn already supports a variable RebootPending - you could use that as a condition to require a reboot. Neil Neil Sleightholm n...@x2systems.com On 14 Jun 2012, at 10:12, Neil Sleightholm wrote: > One option is to set the flag on the sqlexpress install to ignore the pen

Re: [WiX-users] Burn Bootstrapper and SQL Server 2008 R2 Express

One option is to set the flag on the sqlexpress install to ignore the pending restart rule check (/SkipRules=RebootRequiredCheck). It might worth adding a feature request to get a property added to burn to indicate pending restarts. Neil Neil Sleightholm n...@x2systems.com

[WiX-users] Burn Bootstrapper and SQL Server 2008 R2 Express

Hello we have built a bootstrapper that installs different prerequisites, including "SQL Server 2008 R2 Express". This component can only install if there is no pending change on the machine, i.e. if the machine has been rebooted since the last time a setup has written data in the registry value "H