Re: [WiX-users] Setting the version number...
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-installer-xml-wix-toolset.687559.n2.nabble.com/Setting-the-version-number-tp5942903p7581771.html Sent from the wix-users mailing list archive at Nabble.com. -- LogMeIn Central: Instant, anywhere, Remote PC access and management. Stay in control, update software, and manage PCs from one command center Diagnose problems and improve visibility into emerging IT issues Automate, monitor and manage. Do more in less time with Central http://p.sf.net/sfu/logmein12331_d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
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 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 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-installer-xml-wix-toolset.687559.n2.nabble.com/Setting-the-version-number-tp5942903p7581771.html Sent from the wix-users mailing list archive at Nabble.com. -- LogMeIn Central: Instant, anywhere, Remote PC access and management. Stay in control, update software, and manage PCs from one command center Diagnose problems and improve visibility into emerging IT issues Automate, monitor and manage. Do more in less time with Central http://p.sf.net/sfu/logmein12331_d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- LogMeIn Central: Instant, anywhere, Remote PC access and management. Stay in control, update software, and manage PCs from one command center Diagnose problems and improve visibility into emerging IT issues Automate, monitor and manage. Do more in less time with Central http://p.sf.net/sfu/logmein12331_d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Setting the version number...
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. -- LogMeIn Central: Instant, anywhere, Remote PC access and management. Stay in control, update software, and manage PCs from one command center Diagnose problems and improve visibility into emerging IT issues Automate, monitor and manage. Do more in less time with Central http://p.sf.net/sfu/logmein12331_d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Setting the version number...
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;
Version=quot;$(var.ProductVersion)quot;
I compile using VS2010 and get these errors:
Error 4 The Windows Installer XML variable
!(wix.FileVersion.file_TMCResources) is unknown. Please ensure the variable
is declared on the command line for light.exe, via a WixVariable element, or
inline using the syntax !(wix.FileVersion.file_TMCResources=some value which
doesn't contain parenthesis). C:\Dev\Core
Technologies\Main\Setup\TMC_Client_Setup\Product.wxs5 1
TMC_Client_Setup
I have a merge module (which includes the variables.wxi) which contains that
file id:
lt;Component Id=quot;cmp9A893CD17F2583C3B6A49923CB3B231Cquot;
Guid=quot;{SOME_GUID}quot; Permanent=quot;noquot; Shared=quot;noquot;
File Id=file_TMCResources KeyPath=yes
Source=$(var.tmcSourcePath)\TMC_Resources.dll /
/Component
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-version-number-tp5942903p7581390.html
Sent from the wix-users mailing list archive at Nabble.com.
--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
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 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;
Version=quot;$(var.ProductVersion)quot;
I compile using VS2010 and get these errors:
Error 4 The Windows Installer XML variable
!(wix.FileVersion.file_TMCResources) is unknown. Please ensure the
variable
is declared on the command line for light.exe, via a WixVariable element,
or
inline using the syntax !(wix.FileVersion.file_TMCResources=some value
which
doesn't contain parenthesis). C:\Dev\Core
Technologies\Main\Setup\TMC_Client_Setup\Product.wxs5 1
TMC_Client_Setup
I have a merge module (which includes the variables.wxi) which contains
that
file id:
lt;Component Id=quot;cmp9A893CD17F2583C3B6A49923CB3B231Cquot;
Guid=quot;{SOME_GUID}quot; Permanent=quot;noquot;
Shared=quot;noquot;
File Id=file_TMCResources KeyPath=yes
Source=$(var.tmcSourcePath)\TMC_Resources.dll /
/Component
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-version-number-tp5942903p7581390.html
Sent from the wix-users mailing list archive at Nabble.com.
--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
virtually,
Rob Mensching
http://RobMensching.com LLC
--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Setting the version number...
So I have a include file called Variables.wxi which has the define product
version
I have a MergeModule which as the fileID.
The include file is included in both product.wxs and mergemodule.wxs
If I use either the GUID from the component within the merge module or use the
package ID from the merge module it fails:
?define ProductVersion =
!(bind.fileVersion.file_TMCResources.D0328AB9_4135_4C11_9FF7_3887FB6573A6)?
I get:
Error 4 Unresolved bind-time variable
!(bind.fileVersion.file_TMCResources.D0328AB9_4135_4C11_9FF7_3887FB6573A6).
C:\Dev\Core Technologies\Main\Setup\TMC_Client_Setup\Product.wxs5
1 TMC_Client_Setup
Or use this:
?define ProductVersion =
!(wix.FileVersion.file_TMCResources.D0328AB9_4135_4C11_9FF7_3887FB6573A6)?
I get this:
Error 4 The Windows Installer XML variable
!(wix.FileVersion.file_TMCResources.D0328AB9_4135_4C11_9FF7_3887FB6573A6) is
unknown. Please ensure the variable is declared on the command line for
light.exe, via a WixVariable element, or inline using the syntax
!(wix.FileVersion.file_TMCResources.D0328AB9_4135_4C11_9FF7_3887FB6573A6=some
value which doesn't contain parenthesis). C:\Dev\Core
Technologies\Main\Setup\TMC_Client_Setup\Product.wxs5 1
TMC_Client_Setup
Using latest release version of Wix 3.6
Steve
-Original Message-
From: Rob Mensching [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, 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 with:
Product Id=quot;$(var.ProductCode)quot;
Name=quot;$(var.ProductName)quot;
Language=quot;1033quot;
Version=quot;$(var.ProductVersion)quot;
I compile using VS2010 and get these errors:
Error 4 The Windows Installer XML variable
!(wix.FileVersion.file_TMCResources) is unknown. Please ensure the
variable is declared on the command line for light.exe, via a
WixVariable element, or inline using the syntax
!(wix.FileVersion.file_TMCResources=some value which
doesn't contain parenthesis). C:\Dev\Core
Technologies\Main\Setup\TMC_Client_Setup\Product.wxs5 1
TMC_Client_Setup
I have a merge module (which includes the variables.wxi) which
contains that file id:
lt;Component Id=quot;cmp9A893CD17F2583C3B6A49923CB3B231Cquot;
Guid=quot;{SOME_GUID}quot; Permanent=quot;noquot;
Shared=quot;noquot;
File Id=file_TMCResources KeyPath=yes
Source=$(var.tmcSourcePath)\TMC_Resources.dll /
/Component
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-version-number-tp5942903p7581390.html
Sent from the wix-users mailing list archive at Nabble.com.
--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics Download AppDynamics Lite
for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
virtually,
Rob Mensching
http://RobMensching.com LLC
--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics Download AppDynamics Lite for free
today:
http://p.sf.net/sfu/appdyn_sfd2d_oct
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Setting the version number...
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 much better last night! :D Thank you, that did the trick and then some! (http://stackoverflow.com/questions/626033/how-can-i-set-the-wix-installer-version-to-the-curent-build-version says bind rather than wix, which seems to work better) -- Rune -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Setting the version number...
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 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 much better last night! :D Thank you, that did the trick and then some! ( http://stackoverflow.com/questions/626033/how-can-i-set-the-wix-installer-version-to-the-curent-build-version says bind rather than wix, which seems to work better) -- Rune -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- virtually, Rob Mensching - http://RobMensching.com LLC -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Setting the version number...
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: http://morten.lyhr.dk/2007/10/how-to-insert-assembly-version-number.html (which links to the third option) http://vsts-fu.blogspot.com/2009/01/injecting-version-numbers-into-wix.html My idea is this: When I include a project reference, I get all sorts of nice variables defined. Target platform - check. TargetDir - check. Target version... Target version? The one really interesting attribute of my included project is MIA. Is there a possibility this can be included eventually? I suspect this would prove helpful to quite a few users. Or is there already a more elegant solution to this seemingly simple problem? Thanks for all the great help so far guys. -- Rune -- Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Setting the version number...
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 so all installers referring to that include file will get updated appropriately. So far it is working very well for us. We even have an XML file where we store our sprint number in sothat the build server will create a version number in the following format: 1. (sprint).(days since beginning of sprint).(tfs build revision number) Let me know if this might work for you. I think you can apply this to any CI app. On 20 Jan 2011, at 10:24, Rune Moberg jjfl...@gmail.com wrote: 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: http://morten.lyhr.dk/2007/10/how-to-insert-assembly-version-number.html (which links to the third option) http://vsts-fu.blogspot.com/2009/01/injecting-version-numbers-into-wix.html My idea is this: When I include a project reference, I get all sorts of nice variables defined. Target platform - check. TargetDir - check. Target version... Target version? The one really interesting attribute of my included project is MIA. Is there a possibility this can be included eventually? I suspect this would prove helpful to quite a few users. Or is there already a more elegant solution to this seemingly simple problem? Thanks for all the great help so far guys. -- Rune --- --- --- - Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Setting the version number...
Hi, Our builds run a custom TFS build task that checks out a build number file, updates it and checks it back in. This is used as a msbuild property that is passed to our wixprojs which are built from a .sln. In the 'Define preprocessor variables' setion in votive we have a mapping from msbuild buildNumber=$(SdlBuildNumber); In our wix we use e.g. ?define productVersion = 2.0.$(var.buildNumber) ? Which is then used in Product@version and in the upgrade elements, where we can't use the MajorUpgrade element. e.g. Version=$(var.productVersion) We follow the basic versioning scheme for MSIs:- Major.Minor.BuildNumber The msi version is controlled by the deployment team to allow upgrades and patching to work correctly. If marketing want a product to be version 2011 we make the display name into 2011 but just increment the major version by one. So 2011 of one of our products has an msi version of 2.0 The Major version is changed by hand when we do a new full release. These are major upgrades and sometimes side by side installations with the older version. The Minor version is also changed by hand for smaller releases, we call these service packs (2011 SP1 aka 2.1) and deploy as major upgrades. The Build number increments every build and is also applied to the file version of all binaries/assemblies. We don't really use the fourth part of file versions. For compatibility reasons Assembly versions only change when the assembly has been updated. We make cumulative update 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 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 so all installers referring to that include file will get updated appropriately. So far it is working very well for us. We even have an XML file where we store our sprint number in sothat the build server will create a version number in the following format: 1. (sprint).(days since beginning of sprint).(tfs build revision number) Let me know if this might work for you. I think you can apply this to any CI app. On 20 Jan 2011, at 10:24, Rune Moberg jjfl...@gmail.com wrote: 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: http://morten.lyhr.dk/2007/10/how-to-insert-assembly-version-number.html (which links to the third option) http://vsts-fu.blogspot.com/2009/01/injecting-version-numbers-into-wix.html My idea is this: When I include a project reference, I get all sorts of nice variables defined. Target platform - check. TargetDir - check. Target version... Target version? The one really interesting attribute of my included project is MIA. Is there a possibility this can be included eventually? I suspect this would prove helpful to quite a few users. Or is there already a more elegant solution to this seemingly simple problem? Thanks for all the great help so far guys. -- Rune --- --- --- - Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - - Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road
Re: [WiX-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 to that include file will get I was hoping to avoid generating yet another version file. The solution I suggested, having the version extracted from the referenced project, should provide an elegant and self-documenting solution to this. My hope was that this could be considered for a future release of WiX. -- Rune -- Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Setting the version number...
I should also say that in our build process a list of .cs 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 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 to that include file will get I was hoping to avoid generating yet another version file. The solution I suggested, having the version extracted from the referenced project, should provide an elegant and self-documenting solution to this. My hope was that this could be considered for a future release of WiX. -- Rune - - Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. -- Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Setting the version number...
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) On Thu, Jan 20, 2011 at 3:31 AM, David Watson dwat...@sdl.com wrote: I should also say that in our build process a list of .cs 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 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 to that include file will get I was hoping to avoid generating yet another version file. The solution I suggested, having the version extracted from the referenced project, should provide an elegant and self-documenting solution to this. My hope was that this could be considered for a future release of WiX. -- Rune - - Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. -- Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- virtually, Rob Mensching - http://RobMensching.com LLC -- Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
