I have not tested it, but the BuildDependencies has an enumerator and a
Item(index) property to return BuildDependency objects, and each
BuildDependency object has a Project and RequiredProjects properties. So,
given an project, you could know its dependencies.
On the other hand, EnvDTE.BuildEvents should give information about which
Solution/Projects are going to be build.

Signature
Best regards,
Carlos J. Quintero
MZ-Tools: Productivity add-ins for Visual Studio
You can code, design and document much faster:
http://www.mztools.com
>I work on a very large VS2005 solution which has over 75 with mixed C++
>
[quoted text clipped - 32 lines]
> Christopher
> BigHammer Software
DrZogg - 16 Oct 2006 15:59 GMT
Carlos,
As I mentioned, BuildDependencies returns the complete list of
solutions..
How do I find the project this is the primary focus of this build?
that is the real question..
The EnvDTE.BuildEvents tell me the answer after the build is complete.
But that isn't a very nice progress bar... You're supposed to predict
the number
of steps up front, not just announce that you're done.
If there are any more ideas I would love to hear them.
Christopher
> I have not tested it, but the BuildDependencies has an enumerator and a
> Item(index) property to return BuildDependency objects, and each
[quoted text clipped - 50 lines]
> > Christopher
> > BigHammer Software
Carlos J. Quintero [VB MVP] - 17 Oct 2006 08:25 GMT
The EnvDTE.BuildEvents.OnBeginBuild and OnBuildProjConfigBegin should inform
you what is about to be compiled.

Signature
Best regards,
Carlos J. Quintero
MZ-Tools: Productivity add-ins for Visual Studio
You can code, design and document much faster:
http://www.mztools.com
Carlos,
As I mentioned, BuildDependencies returns the complete list of
solutions..
How do I find the project this is the primary focus of this build?
that is the real question..
The EnvDTE.BuildEvents tell me the answer after the build is complete.
But that isn't a very nice progress bar... You're supposed to predict
the number
of steps up front, not just announce that you're done.
If there are any more ideas I would love to hear them.
Christopher
jmatejka@gmail.com - 18 Oct 2006 17:08 GMT
I'm interested in a similar topic. Carlos, I think you are
misunderstanding. Knowing that something is about to be compiled the
instant before it is compiled is not useful in this instance. I (I
belive DrZogg also) want to know what projects will be compiled at the
beginning of the entire build process.
Thanks,
Justin
> The EnvDTE.BuildEvents.OnBeginBuild and OnBuildProjConfigBegin should inform
> you what is about to be compiled.
[quoted text clipped - 24 lines]
>
> Christopher
jmatejka@gmail.com - 18 Oct 2006 22:28 GMT
Maybe there is a combination solution where we can figure out the
dependencies with
IVsBuildDependencies, and which projects are dirty with
IVsBuildStatusCallback.
Then with that information we can walk along the dependency tree and
calculate the total number of projects that need to be built.
Could this work? Is there some easier way?
- Justin
> I'm interested in a similar topic. Carlos, I think you are
> misunderstanding. Knowing that something is about to be compiled the
[quoted text clipped - 33 lines]
> >
> > Christopher