1) Recommend changing the instructions on specifying an MSBuild to add "bin" to the directory path. The reason for this is if you have custom actions that require the binaries in the SDK directory, this directory is not part of the current instructions. Also build tasks in the SDK directory refer to the binaries in the bin directory via relative pathways.
<wix_v3>+--bin
|
+--sdk</wix_v3>
2) For ease of change, recommend separating the Wix build version into a separate property, which is then used to build subsequent pathway properties. Thus when you update your project, other than copying the new wix build binaries into source control, the only change required is to modify a single project property.
Below is my current Wix property group.
<propertygroup>
<wixversion>v3.0.4624.0</wixversion>
<wixtoolpath>$(SolutionRoot)\WiX_v3\$(WixVersion)\bin\</wixtoolpath>
<wixtargetspath>$(WixToolPath)Wix.targets</wixtargetspath>
<wixtaskspath>$(WixToolPath)wixtasks.dll</wixtaskspath>
</propertygroup>
I added a note about the SDK directory. I mentioned the idea of using a versioned directory for the tools, but in my experience, most groups expose a last-known-good version of tools rather than always referring to version number in source control and build scripts.
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 21 days (the time period specified by
the administrator of this Tracker).