Re: [WiX-users] WixPdbPath property

Just to close the loop on this, WiX 3.8 will be removing WixPdbPath: http://wixtoolset.org/issues/4152/ robmen wrote > Many people move it to a drop location that is laid out identically as the > build machine with a different root. We can work with that. pyro already > has support for such gymna

Re: [WiX-users] define variable =x if another variable is y else =z

KristjanLaane wrote > i.e. is it possible to set a variable value based on another variable > value? Sure, you can use the WiX's Conditional Preprocessor Statements . -- View this message in context: http://windows-

[WiX-users] Is there a WiX 4.0 replacement for candle.exe -trace?

The -trace command line switch was removed in WiX 4.0 and deprecated in WiX 3.9 . Is there a replacement for this functionality going forward? This added the message to the end of an error: Source trace: at C:\source\driver.wxs: line 54 -- View this messa

Re: [WiX-users] Is there a WiX 4.0 replacement for candle.exe -trace?

I dug around in the lists and and changes and just couldn't find any mention of why it was removed. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Is-there-a-WiX-4-0-replacement-for-candle-exe-trace-tp7597729p7597732.html Sent from the wix-users m

Re: [WiX-users] Is there a WiX 4.0 replacement for candle.exe -trace?

Yes, we used this switched in our build system since WiX 3.0 to provide additional debugging information. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Is-there-a-WiX-4-0-replacement-for-candle-exe-trace-tp7597729p7597738.html Sent from the wix-u

Re: [WiX-users] Is there a WiX 4.0 replacement for candle.exe -trace?

We enabled -trace by default a long while ago, but it looks like no one ever realized that it was just duplicated information. I'll remove this from our build tools. without -trace: > C:\source\driver.wxs(3) : fatal error CNDL0023: Undefined variable: > $(var.Manufacturer). with -trace: > C:\s

Re: [WiX-users] Naming convention of "heat.exe" harvested comp and file id.

But remember, if you install a file with the same name into two different folders, you'll need the file Ids to be unique. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Naming-convention-of-heat-exe-harvested-comp-and-file-id-tp7597821p7597832.htm

Re: [WiX-users] Adjusting result of heat.exe?

The -cg is what you need to get you exactly what you are asking for. I use it myself. http://wixtoolset.org/documentation/manual/v3/overview/heat.html wrote > -cg > > Component group name (cannot contain spaces e.g -cg MyComponentGroup). -- View this message in context: http://windows-ins

Re: [WiX-users] How does heat maintain consistent GUIDs?

Also see Rob's response here: http://stackoverflow.com/questions/16120473/wix-is-it-safe-to-use-autogenerated-guid-on-component-tags -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-does-heat-maintain-consistent-GUIDs-tp7599757p7599762.html Sent