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
version from the wxi (or from the bundle, if we are able to reference the
version of msi package)?
--
View this message in context:
See http://wix.sourceforge.net/manual-wix3/light.htm
Section Package Properties
Dirk
On Tue, Nov 6, 2012 at 12:39 PM, Goran malov...@yahoo.com 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
Thanks, that worked fine.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Setting-the-version-number-tp5942903p7581782.html
Sent from the wix-users mailing list archive at Nabble.com.
Hi Rob,
I have a wxi variable file with:
?define ProductVersion = !(wix.FileVersion.file_TMCResources)?
then my product.wxs file with:
Product Id=quot;$(var.ProductCode)quot;
Name=quot;$(var.ProductName)quot;
Language=quot;1033quot;
Merge Modules modularize the identifiers (append the .G_U_I_D). So you
must do that too.
On Tue, Oct 16, 2012 at 2:15 PM, StevenOgilvie sogil...@msn.com wrote:
Hi Rob,
I have a wxi variable file with:
?define ProductVersion = !(wix.FileVersion.file_TMCResources)?
then my product.wxs file
XML toolset.
Subject: Re: [WiX-users] Setting the version number...
Merge Modules modularize the identifiers (append the .G_U_I_D). So you must
do that too.
On Tue, Oct 16, 2012 at 2:15 PM, StevenOgilvie sogil...@msn.com wrote:
Hi Rob,
I have a wxi variable file with:
?define
On Thu, Jan 20, 2011 at 2:01 PM, Rob Mensching r...@robmensching.com wrote:
If you don't want to generate another file (this is what WiX does), then my
new favorite trick is to do:
Product/@Version=!(wix.FileVersion.SomeFileIdInYourMsi)
Had I read your e-mail yesterday, I would have slept
Yeah, sorry, there are some anachronisms in the binder variables that are
not stored in my memory correctly because I spend too much time thinking
about how they need to be fixed. smile/
On Fri, Jan 21, 2011 at 12:20 AM, Rune Moberg jjfl...@gmail.com wrote:
On Thu, Jan 20, 2011 at 2:01 PM, Rob
I have googled my eyes out recently, trying to figure out an easy way
of setting my installer's version number to match that of my product.
I found three alternatives. None of them appeals to me, because they
are either kludgy, involves some kind of plug-in or ...well, kludgy:
Hi Rune
I haven't checked your links but what we use is the Tfs build server's
ability to download the new source from repo, look for all
assemblyinfo.cs files and update the version numbers. Then using a wix
include file using the variable holding version 1.0.0.0 we update that
file and
MSPs that we deploy automatically with True Update.
Dave
-Original Message-
From: Dandre [mailto:dandre...@gmail.com]
Sent: 20 January 2011 09:22
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Setting the version number...
Hi Rune
I haven't checked your
On Thu, Jan 20, 2011 at 10:21 AM, Dandre dandre...@gmail.com wrote:
assemblyinfo.cs files and update the version numbers. Then using a wix
include file using the variable holding version 1.0.0.0 we update that
file and so all installers referring to that include file will get
I was hoping to
-users] Setting the version number...
On Thu, Jan 20, 2011 at 10:21 AM, Dandre dandre...@gmail.com wrote:
assemblyinfo.cs files and update the version numbers. Then using a wix
include file using the variable holding version 1.0.0.0 we update that
file and so all installers referring
are updated
automatically from the master build number.
-Original Message-
From: Rune Moberg [mailto:jjfl...@gmail.com]
Sent: 20 January 2011 11:20
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Setting the version number...
On Thu, Jan 20, 2011
14 matches
Mail list logo
