Follow-up.... Our old VS2012 solution was organized like this...
A.vsxproj (C++) B.csproj (C#) C.csproj (C#) W.wixproj (WiX) Where project-B had a SOLUTION dependency on the C++ project-A. And the WiX project has project dependencies on both project-B and project-C. When built via VS2012, the solution build order would be A, B, C, W. However, when MSBuild built this solution, the build order A, C, W, B. As expected, building project-W would fail because project-B's output was nowhere to be found. I followed the instructions in the link Rob provided and removed the SOLUTION dependency between project-B and project-A. Instead, I manually edited project-B's csproj file to add a PROJECT dependency to project-A (VS2012 won't let you add a C++ as a project reference to a C# project). After reloading project-B, I now see project-A in project-B's References list. Though, depending on VS2012 mood at the time, it may or may not have a little yellow triangle next to project-A's entry. Now via both VS2012 and MSBuild, the build order is A, B, C, W. I still don't quite understand why the changes make it work, but I'm glad it does.<g> On Wed, May 28, 2014 at 6:19 PM, Rob Mensching <r...@firegiant.com> wrote: > Sounds a lot like: > http://blogs.msdn.com/b/msbuild/archive/2010/12/21/incorrect-solution-build-ordering-when-using-msbuild-exe.aspx > > _______________________________________________________________ > FireGiant | Dedicated support for the WiX toolset | > http://www.firegiant.com/ > > -----Original Message----- > From: Tony [mailto:yellowjacketl...@gmail.com] > Sent: Wednesday, May 28, 2014 1:56 PM > To: WiX Users > Subject: [WiX-users] Build order problems Votive vs MSBuild > > We've run into this issue in which it appears as though our .sln builds > correctly when built through VS (Votive installed), but when built using > MSBuild, the WiX project dependencies appear to be ignored. This results > in a build order problem (csproj is built _after_ wixproj that needs its > output). If the build order is forced (manually add a dependency in the > sln file), the MSBuild build works fine. As such, it appears as if MSBuild > is used on the .sln, the auto generated project dependency list (and thus > build order) is not correct. > > NOTE: We do NOT have WiX installed on our build server. I have modified > our wixproj files per > http://wixtoolset.org/documentation/manual/v3/msbuild/daily_builds.html. > > I found an old thread titled "Problem with build order under MSBuild 4.0" > (4/14/10) that describes an identical issue. And another thread titled > "Wix3.6.1518.0 to 3.6.1915.0 issue" (7/20/11) in which this bug > http://sourceforge.net/p/wix/bugs/2588/ is linked. But I can't tell if > the bug was fixed or just closed. > > Any ideas? > > VS/TFS2012, Wix 3.8 > -- > Tony > > ------------------------------------------------------------------------------ > Time is money. Stop wasting it! Get your web API in 5 minutes. > www.restlet.com/download > http://p.sf.net/sfu/restlet > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > ------------------------------------------------------------------------------ > Time is money. Stop wasting it! Get your web API in 5 minutes. > www.restlet.com/download > http://p.sf.net/sfu/restlet > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- Tony ------------------------------------------------------------------------------ Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/NeoTech _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
