Re: [WiX-users] Setting the version number...

See http://wix.sourceforge.net/manual-wix3/light.htm Section "Package Properties" Dirk On Tue, Nov 6, 2012 at 12:39 PM, Goran wrote: > Has there been an improvement regarding this issue? We can use !bind > without > any problems from the msi wxs file, but I could not find a way to get > vers

Re: [WiX-users] WiX 3.6 MergeModule creation regression?

will do! Dirk -- Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try

Re: [WiX-users] WiX 3.6 MergeModule creation regression?

Hello Rob, here is a minimal mergemodule showing the error: http://schemas.microsoft.com/wix/2006/wi";>

[WiX-users] WiX 3.6 MergeModule creation regression?

this case, because the final product must be a merge module. Thank you in advance Dirk -- Dirk Ziegelmeier * d...@ziegelmeier.net * http://www.ziegelmeier.net -- Don't let slow site performance ruin your business. Dep

Re: [WiX-users] Detect perUser install from perMachine install (Launchcondition)

Thank you Peter, I should be able to make it work using your information! That's what I was looking for. Dirk -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat l

[WiX-users] Detect perUser install from perMachine install (Launch condition)

Hello, I'd like to author an MSI that shall upgrade an old (non-WiX) setup. The old setup had an option where it could either be installed perMachine or perUser. The new setup should be perMachine only, so I'd like to write a launch condition that reads "Please uninstall old [Product] before insta

Re: [WiX-users] Wix upgrade process does not consider 4th part of the version string

Hi, read this thread. Maybe this is what you need: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Setup-upgrade-needs-to-care-for-4th-part-of-version-number-td3250189.html Dirk On Fri, Jan 14, 2011 at 23:55, Wilson, Phil wrote: > That's a Windows Installer limitation on upgrad

Re: [WiX-users] Question about register .net COM object

Hello, this is a working example of a COM object registration: Examples for the defines: D_Product_Fqn: Adm2.Adm.Dtm, Version=1.0.0.0, Culture=neutral, PublicKeyToken=7b26e28fb8781288 C_DtmClass: Adm2.Adm.Dtm.Adm D_ProductImageRuntime: v1.1.4322 C_DtmClassId: C_DtmPr

Re: [WiX-users] KeyPath problem that I do not understand

that this is fixed in > v3.5. > > -----Original Message- > From: Dirk Ziegelmeier [mailto:d...@ziegelmeier.net] > Sent: Thursday, September 17, 2009 5:42 AM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] KeyPath problem that I do not understand &

Re: [WiX-users] KeyPath problem that I do not understand

, Bob Arnson wrote: > Dirk Ziegelmeier wrote: >> The line causing the error is "> Name="[MergeRedirectFolder]ConstantNameB"..." so the problem seems to >> be the property substitution in there. >> *** But this RegistryValue is NOT the KeyPath of th

Re: [WiX-users] KeyPath problem that I do not understand

Hello again, my code fragment can even be simplified (no need for two "RegistryKey" entries):                         Dirk -- Come build with us! The BlackBerry® Developer Conference in SF, CA is the only devel

[WiX-users] KeyPath problem that I do not understand

Hello all, I have the following code fragment in my merge module (Notice: Guid="*"):                                 The fragment above works. However, if I include the line that is commented out above, I get the following error: error LGHT0230 : The Component/@Guid attribute's value '

Re: [WiX-users] Setup upgrade needs to care for 4th part of version number

ith the same 3 part number will never go live you should be ok. > > If you search back through the list you should find a discussion about > doing this. > > Neil > > Neil Sleightholm > X2 Systems Limited > n...@x2systems.com <mailto:n...@x2systems.com> &g

[WiX-users] Setup upgrade needs to care for 4th part of version number

Hello All, due to political issues (see below) my setups need to be able to upgrade when only the 4th part of the version info changes. Example: V1.0.0.1 needs to upgrade V1.0.0.0. My installers always do major upgrades, the product GUI always changes (that is OK and not an issue to discuss). Af