I'm not sure what you mean by "unbound" wixlibs, but I do have a setup like this...
a.csproj b.csproj wl.wixproj <-- references a and b to make a wixlib wx.wixproj <-- references wl.wixproj to make the msi But again, I still had an issue when the PreBuild and/or BeforeBuild actions ran on wl.wixproj. They would run either before a.csproj or before b.csproj, but never before (except when built via VS) wl.wixproj like I wanted. Thanks for the test project file. When I get some downtime I'll give it a try. Maybe it will help me understand the MSBuild build order that has plagued me. I really hope Microsoft drops the current solution file format and replaces it with a true MSBuild project file. I think that would make some of these issues easier to resolve. On Tue, Aug 12, 2014 at 1:20 PM, Phill Hogland <phogl...@rimage.com> wrote: > > In an earlier post in this thread I described a foolish approach for > reusing > common code using batch scripts and copying wxs files between projects. > Creating 'unbound' wixlibs is a much easier approach to manage! > > -- Tony ------------------------------------------------------------------------------ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
