How does that translate into usage by developers? Where is [[Version]] pulled from?
I see the following at the top of my wixproj files <Project ToolsVersion="4.0" DefaultTargets="Build" xmlns="http://schemas.microsoft.com/developer/msbuild/2003";> <Import Project="../../WiXVersioning.targets" /> <PropertyGroup> <Configuration Condition=" '$(Configuration)' == '' ">Debug</Configuration> <Platform Condition=" '$(Platform)' == '' ">x86</Platform> <ProductVersion>3.7</ProductVersion> I'm assuming I should put the propertygroup you mentioned below the ProductVersion and replace [[Version]] with $(ProductVersion). And even then, to that end I would likely just stick all of these things in my existing WiXVersioning.targets file so all wixproj files get the changes from one place. Also, I'm assuming the zip file's .target files take care of the difference in the folder structure. In the wix3.9-binaries we have ./sdk/inc ./sdk/vs20XX/lib ./x64 ./x86 >From the installer we have ./sdk ./sdk/VS20XX/lib (I'll ignore the case difference because this is windows I'm concerned about, not mono) ./sdk/VS20XX/inc There is an inc folder in each version of VS for the installer. Shouldn't this be one inc file and multiple lib folders as it is in the zip? This seems to be a bug in the installer to me. Also, in the zip there is no bin folder. Everything from the bin folder is just in the root, including ./x86. Would we be able to update one or the other before RTM and get this addressed? How does this currently get addressed? How do the wix.targets and wix20XX.targets files address the complete difference in disk footprint that these two deployment strategies present? Right now we are moving files around from the zip to match the directory structure of what is laid down in the installer so that things actually compile. Stephen Tunney Nuance Communications, Inc. Solutions Architect, Imaging Division Waterloo, Ontario, Canada stephen.tun...@nuance.com 519-880-7463 Office NUANCE.COM The experience speaks for itself (tm) -----Original Message----- From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] Sent: October-02-14 2:54 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] WiX 3.x Installs are mutually exclusive. Why? :) You don't need WiX installed to use it. Check out the "Integrating WiX Projects Into Daily Builds" topic in the help file. Short version is to download the binaries zip, put it in a known location on your build machine, and then use <PropertyGroup> <WixToolPath>$(SourceCodeControlRoot)\wix\[[Version]]\</WixToolPath> <WixTargetsPath>$(WixToolPath)Wix.targets</WixTargetsPath> <WixTasksPath>$(WixToolPath)wixtasks.dll</WixTasksPath> </PropertyGroup> in your project to point it at the desired WiX version. -----Original Message----- From: Tunney, Stephen [mailto:stephen.tun...@nuance.com] Sent: Thursday, October 02, 2014 1:29 PM To: General discussion about the WiX toolset. Subject: [WiX-users] WiX 3.x Installs are mutually exclusive. Why? :) Hey guys, Just ramping up to upgrade from 3.7 to 3.9 and it appears as though I can only have 1 version installed (via the installer) at a time on my development box. This has me a touch concerned. I would really like to maintain older versions of our product with the version of WiX that generated the RTM installer. I think this would be essential for generating patches, etc. Also, I have noticed that the SDK folder structure in the ZIPs in 3.9 (and 3.8) do not match the directory structure of the installer. Is there a reason for this? Cheers, Stephen Tunney Nuance Communications, Inc. Solutions Architect, Imaging Division Waterloo, Ontario, Canada stephen.tun...@nuance.com<mailto:stephen.tun...@nuance.com> 519-880-7463 Office NUANCE.COM The experience speaks for itself (tm) ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
