The build ordering you expect here is C, then B, then A, and Visual Studio shows that correctly in the Build Order tab, as you see below. Below I’ve shown the context menu and what you see in the dialog when you have this setup. This manually specified dependency was set up in the solution by right clicking on the solution and choosing Project Dependencies…, then checking a box. I’ve shown regular project references with solid lines, and the information in the solution with dotted lines. At the same time in the solution file, there is a manually specified dependency: B depends on C. Let’s say they are C# projects.Ī has a regular project reference to B, so it will invoke B, then when B comes back done, it will build itself. This diagram shows a solution file containing three projects, A, B, and C. If you’re not interested in the “why”, skip ahead to the workaround. #BUILD MULTIPLE SOLUTIONS IN VISUAL STUDIO FOR MAC FULL#Here’s a full description of what’s going on, why it began in 4.0, and the fix we recommend to your projects to solve the problem. We’ve had a few reports of cases where Visual Studio, and previous versions of MSBuild, will build the projects in the solution in the correct order, but the 4.0 version of MSBuild.exe gets the order wrong. As always, feedback is welcome! Please leave your comments in this blog post and report any bugs on Microsoft Connect. UPDATE: This issue has been fixed in Visual Studio 11/NETFX45.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |