Hi Jim,
Thanks a lot for the info. I had not had time to download 2013 RTM but am doing it now.
The latest (unreleased) 5.1 codebase already incorporates WiX 3.7. It also looks for a locally installed WiX before using the bundled version. If WiX 3.8 comes out and someone installs it, the Deployment Framework will pick it up and use it (assuming the WiX team doesn't change around their registry keys). It's also possible now to override a WixDir property and point to wherever you have the WiX binaries. I have one project where the WiX binaries are in a Dependencies\WiX\v3.7 folder in TFS, and we just point to that copy (with WixDir) in the .btdfproj and map it into a TFS build workspace along with the code.
I'll look into the SSOClient issue.
Thanks,
Tom
Thanks a lot for the info. I had not had time to download 2013 RTM but am doing it now.
The latest (unreleased) 5.1 codebase already incorporates WiX 3.7. It also looks for a locally installed WiX before using the bundled version. If WiX 3.8 comes out and someone installs it, the Deployment Framework will pick it up and use it (assuming the WiX team doesn't change around their registry keys). It's also possible now to override a WixDir property and point to wherever you have the WiX binaries. I have one project where the WiX binaries are in a Dependencies\WiX\v3.7 folder in TFS, and we just point to that copy (with WixDir) in the .btdfproj and map it into a TFS build workspace along with the code.
I'll look into the SSOClient issue.
Thanks,
Tom