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.
--
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
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:
http://windows-i
ching [mailto:r...@robmensching.com]
Sent: October-16-12 5:54 PM
To: General discussion for Windows Installer 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,
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 wrote:
> Hi Rob,
>
> I have a wxi variable file with:
>
>
> then my product.wxs file with:
> Name="$(var.ProductName)"
>Language="1
Hi Rob,
I have a wxi variable file with:
then my product.wxs file with:
Must be an easy way to read a fileversion and use that as your
productversion?
Steve
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Setting-the-v
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.
On Fri, Jan 21, 2011 at 12:20 AM, Rune Moberg wrote:
> On Thu, Jan 20, 2011 at 2:01 PM, Rob Mensching
> wrote:
> >
On Thu, Jan 20, 2011 at 2:01 PM, Rob Mensching 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 much better last ni
files 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
-users] Setting the version number...
On Thu, Jan 20, 2011 at 10:21 AM, Dandre 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
On Thu, Jan 20, 2011 at 10:21 AM, Dandre 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 avoid generating y
s 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 checke
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 s
13 matches
Mail list logo
