C# projects building unnecessarily

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Mark Rendle - 14 Sep 2005 11:10 GMT

Just recently, one of the projects in my C# solution has started getting
rebuilt every time I run a project which is dependent on it, instead of just
saying "The project is up-to-date." It hasn't changed; in fact, it's not
checked out of source control, so it can't be changing. And it's very
annoying, because it's referenced by several other projects, which therefore
also rebuild every time.

Is there any reason why this could be happening? And a way to stop it?

Thanks in advance
Mark

Reply to this Message

Kevin Spencer - 14 Sep 2005 19:37 GMT

Have you checked the Configuration Manager?

Signature

HTH,

Kevin Spencer
Microsoft MVP
.Net Developer
Neither a follower nor a lender be.

> Just recently, one of the projects in my C# solution has started getting
> rebuilt every time I run a project which is dependent on it, instead of
[quoted text clipped - 7 lines]
> Thanks in advance
> Mark

Reply to this Message

Mark Rendle - 15 Sep 2005 10:22 GMT

For what? It's a valid part of the solution, and if it changes then it
should be rebuilt as a dependency. What I don't understand is why it's
building every time when it hasn't changed at all.

> Have you checked the Configuration Manager?
>
[quoted text clipped - 9 lines]
>> Thanks in advance
>> Mark

Reply to this Message

Kevin Spencer - 15 Sep 2005 13:53 GMT

Sorry. I misunderstood the question. So, you're building a different project
which has a dependency on the one that is not changed. In fact, it sounds
like you're saying that you're RUNNING a project that has a dependency on
the one that is not changed, and that other projects which have a dependency
on the unchanged project are being rebuilt as well?

If so, you're talking about 2 different issues:

1. Running a project with a dependency on another project which has not
changed is causing the other project to be rebuilt. How are you confirming
this? Satellite assemblies should be rebuilt, but not the assembly itself.
Also, when you run a project (rather than just rebuilding it), the Output
Window is cleared when your project starts. So, how are you trapping the
output?

2. Other projects which have a dependency on the project which is being
built because of the dependency on it by the running project are being built
as well. This simply should not occur. Have you checked the dependencies for
each project is the Solution Properties "Project Dependencies" dialog?

Signature

HTH,

Kevin Spencer
Microsoft MVP
.Net Developer
Neither a follower nor a lender be.

> For what? It's a valid part of the solution, and if it changes then it
> should be rebuilt as a dependency. What I don't understand is why it's
[quoted text clipped - 13 lines]
>>> Thanks in advance
>>> Mark

Reply to this Message

Mark Rendle - 29 Sep 2005 15:38 GMT

Basically, every time I run my solution, even if I haven't changed ANYTHING
at all, this one project (and thus all projects which reference it) gets
rebuilt and shows the "0 errors, 0 warnings" message instead of the "Project
is up-to-date" message. (The Output window doesn't get cleared, it just
switches to the "Debug" view when the application starts; you can switch it
back to the "Build" view in the dropdown at the top to see the results of
the build process.) It's not all the projects in the solution, because there
are several projects further up the dependency hierarchy which don't get
rebuilt. It's just this project, and any of the other projects which depend
on it. It's most annoying and time-consuming.

Cheers,
Mark

> Sorry. I misunderstood the question. So, you're building a different
> project
[quoted text clipped - 19 lines]
> for
> each project is the Solution Properties "Project Dependencies" dialog?

Reply to this Message

C# projects building unnecessarily

Free Magazines