On 07-May-14 13:42, Eric Schultz wrote: > What isn't causing the problem? :) We need the Wix.dll, plus its > dependencies built, to build Votive. To do that from a Solution file, > we need the Wix project and their dependencies included in the > solution. Doing that causes the first build of Wix after a clean to > fail, but, don't worry, it works the second time. That's probably > easily fixable but I haven't gotten to it yet.
The same is (or at least was) true with all WiX .sln files. > Then Votive VSIX (or it's MSI equivalent) should include the Wix.dll > since it's a dependency. Votive itself doesn't use wix.dll directly (last time I checked) but it's useless without a full toolset install, including MSBuild. Hmmm...VSIXs don't have a lot of deployment power, but I assume it could include a full toolset. It wouldn't work to run a command-line build, but the toolset installer could theoretically be installed at the same time. It's a big change to do a VSIX-style per-user install. But really it's no different than the instructions in the .chm about how you can check in the WiX binaries and redirect the import of wix.targets (which is basically what NuGet would do for you). > The code builds if you eliminate the solution file and the changes > that are required to make it "almost" work in the solution file. > Either way, fitting it into the Wix build process is difficult and > rather touchy. If you don't do things exactly right, things won't > build and it's really confusing as to why. The build doesn't use any .sln file; everything's driven by projects and project references. Since we don't use them in the build, .slns don't get the attention that keeps them fully functional and correct. > I think I'm already there.:) BTDT (t-shirt optional). > I think it'd be easier if Votive was in a totally different repo and > depended on Wix like a third party component would. Whether that's via > Wix shipped as a NuGet package which your VSIX and templates use > (that'd be slick if it worked well) or if it just uses the tools from > Program Files, I think it'd make developing Votive simpler. You > wouldn't have to worry that you need to modify something like > WixBuild.targets or WixBuild.props or override it. Historically, Votive and the core toolset were more tightly bound, as they were both developed simultaneously. Votive was also where the MSBuild targets originated. But that's just history. I whiteboarded an idea about breaking Votive out, mostly with the fantasy that Votive could support multiple toolset versions like VS languages do. Then WiX could be side-by-side. > All that said, while it may look like a great idea to me now, once I > actually get into it, I guarantee there will be headaches that I'm not > foreseein Naturally. :) I'll happily encourage and support (where I can) any experimentation you want to do with Votive. Its current level of functionality means that it mostly work through MSBuild so it's fairly loosely coupled with a particular toolset. We have a decent chunk of time for WiX v3.10 to make bigger changes. -- sig://boB http://joyofsetup.com/ ------------------------------------------------------------------------------ Is your legacy SCM system holding you back? Join Perforce May 7 to find out: • 3 signs your SCM is hindering your productivity • Requirements for releasing software faster • Expert tips and advice for migrating your SCM now http://p.sf.net/sfu/perforce _______________________________________________ WiX-devs mailing list WiX-devs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-devs
