As I reported, I succeeded in creating an "unofficial Official" build, in the sense that it did a full compile without any errors or skipping any part of the build. This gets me back to the point where if I recompile both my compiler extensions and my project tree of msi setups and bundles against this "unofficial Official" build the mba cannot display the UX on another system. It creates the UX on the system where it was compiled. Prior to this I created a test case using WixStdBA, made the necessary changes to address 4592, and tested that debug build on Windows 7 x64 and Windows 8 x64.
The reason I am trying to do an "unofficial Official" build is because of the following statement and an effort to do thorough testing. From: http://wixtoolset.org/development/ "Code your change and test it. Review our code style and write consistent code throughout the project. Remember to build WiX in both debug and release modes, and to run test\test.bat to make sure nothing is broken." There is a link in the above text at 'build', wich says: Official builds with strong-name signing Strong-name signing a WiX build lets it be used on a machine other than the one used to build WiX. Creating an "official unofficial" WiX build requires all the above prerequisites; you can't skip parts of an official build. In general, it's a lot easier to submit a pull request and get the next interim build of WiX. To create a build that can be installed on different machines, create a new strong name key pair and point OFFICIAL_WIX_BUILD to it: sn -k wix.snk sn -p wix.snk wix.pub sn -tp wix.pub Copy the public key and add new InternalsVisibleTo attributes in src\Votive\votive2010\vssdk\AssemblyInfo.cs. Then run the build: msbuild /p:Configuration=Release /p:OFFICIAL_WIX_BUILD=C:\wix.snk So how should I proceed with testing this issue? Try figure out why I am having issues creating an "Official Unofficial" build or (figure out the prior discussion about rebasing) and submit a pull request? Also I ran the test\test.bat again and observed the same red results reported previously. The tests are still running with warnings that runtime tests are not enabled. Should they be? Most tests have an exit code of 0, but there are some other result codes. I'm not confident that I understand what to expect. (And eventually I got the "MSBuild has stopped working" dialog just like last time.) Thanks for any advice! -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/4592-RestartResource-solution-and-review-tp7598149p7598360.html Sent from the wix-devs mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk _______________________________________________ WiX-devs mailing list WiX-devs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-devs
