"Mark Rendle" <markdotrendleatcomputersoftwaredotcom> wrote in message
news:eXng$NQxFHA.3312@TK2MSFTNGP09.phx.gbl...
> 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
>
> "Kevin Spencer" <kevin@DIESPAMMERSDIEtakempis.com> wrote in message
> news:%23VssDSfuFHA.3764@TK2MSFTNGP09.phx.gbl...
>> 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?
>>
>> --
>> HTH,
>>
>> Kevin Spencer
>> Microsoft MVP
>> .Net Developer
>> Neither a follower nor a lender be.
>
>

"Kevin Spencer" <kevin@DIESPAMMERSDIEtakempis.com> wrote in message
news:%23VssDSfuFHA.3764@TK2MSFTNGP09.phx.gbl...
> 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?
>
> --
> HTH,
>
> Kevin Spencer
> Microsoft MVP
> .Net Developer
> Neither a follower nor a lender be.