Visual Studio and .NET Framework Home
EnvDTE.SolutionBuild.Build only builds the startup project [reopen of two old bugs with better reproduce steps]
as By Design
1/2/2008 2:47:55 AM
User(s) can reproduce this bug
Please reopen bugs 106159 and 216699.
I've found the reason why you can't reproduce it - see "Steps to Reproduce".
These old bugs are still in Visual Studio 2008.
Visual Studio 2008 (All Products and Editions)
Operating System Language
Steps to Reproduce
The important info to reproduce the problem is to change a option in Visual Studio:
Tools - Options - Projects and Solutions - Build and Run:
Check "Only build startup projects and dependencies on Run"
For additional steps please see bug 106159 and 216699.
EnvDTE.SolutionBuild.Build honors the "only build startup[..]"
EnvDTE.SolutionBuild.Build should build the whole solution
TAP Code (if applicable)
You can indicate your satisfaction with how Microsoft handled this issue by completing this quick
3 question survey
to post a comment.
Please enter a comment.
on 8/26/2011 at 12:50 AM
This error occurs also in VS2010
on 5/9/2011 at 4:54 PM
this sucks, SolutionBuild.Build() doesn't build the solution, and SolutionBuild.BuildProject() doesn't use the correct configuration! :(
on 8/25/2008 at 2:55 PM
The issue with both Solution.Build and BuildProject not building dependent projects is quite troubling.
Especially given the fact the same behavior is exhibited from even calling Vs services directly.
As a note with VS2003 the build behavior was correct.
Nels P. Olsen
on 6/19/2008 at 1:46 PM
I agree with Carlos. This has nothing to do with "Run".
There appears to be no workaround. Even if I programatically set HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\<Version>\General\BuildStartupsOnlyOnRun in the registry just before I want to do the solution build (after Visual Studio is open), it does not get picked up.
Carlos J. Quintero
on 2/29/2008 at 12:26 AM
Your explanation doesn't make sense because nobody is talking about "Run" here, we are talking about "Build". If I request programmatically SolutionBuild.Build, I expect the whole solution to be built. If I request programmatically to run the solution, you can honor that setting.
on 1/31/2008 at 5:29 PM
Hi Jtb - thanks for posting this issue on Microsoft Connect.
The behavior you describe is "By Design" - DTE follows the Tools/Options settings. You may like to consider using SolutionBuild.BuildProject() to build a specific project.
Please reactive this bug if you have further issues with this.
Ken Watson - Visual Studio Platform
on 1/2/2008 at 6:21 PM
Thanks for your feedback.
We are escalating this issue to the appropriate group within the Visual Studio Product Team for triage and resolution.
These specialized experts will follow-up with your issue.
Visual Studio Product Team
on 1/2/2008 at 6:13 PM
Thank you for your feedback. We are currently investigating. The investigation process normally takes 7-14 days. If this issue is urgent, please contact support directly (see http://support.microsoft.com).
If at any time your issue is closed unsatisfactorily, you may edit your issue via Connect and change the status to “Active.”
Visual Studio Product Team
to post a workaround.
Please enter a workaround.
on 6/30/2010 at 11:52 AM
A possible workaround for this problem:
for (; ; )
var buildState = solutionBuild.BuildState;
if (buildState != vsBuildState.vsBuildStateInProgress)
© 2013 Microsoft