Say ... does anyone know of a good (perhaps free) .NET assembly dependency
walker? Because when you have a project A with a reference B which is also a
reference of C, and C is also a reference of A, and you recompile B in
project A but not C, you get that error "Dependency B.dll in project A
cannot be copied to build directory because it would overwrite the
dependency (old version of B.dll)", but it doesn't tell you that the old
version of B is referenced by C, so you have to go open project C and see
whether B actually is a dependency, and sometimes there are four or five
possible C's, and you can't remember where you used B, so it takes a while,
and you have to rebuild so much and put so much bother into it, that it
would be easier to see exactly which projects you need to rebuild and and
which you don't...

Chris

Do a search for ADepends on your system. The sourcecode should come with
Visual Studio. Just run NMAKE and you're away.

Cheers,

4Space

"Chris Capel" <(E-Mail Removed)> wrote in message
news:%23w1O%(E-Mail Removed)...
> Say ... does anyone know of a good (perhaps free) .NET assembly dependency
> walker? Because when you have a project A with a reference B which is also
a
> reference of C, and C is also a reference of A, and you recompile B in
> project A but not C, you get that error "Dependency B.dll in project A
> cannot be copied to build directory because it would overwrite the
> dependency (old version of B.dll)", but it doesn't tell you that the old
> version of B is referenced by C, so you have to go open project C and see
> whether B actually is a dependency, and sometimes there are four or five
> possible C's, and you can't remember where you used B, so it takes a
while,
> and you have to rebuild so much and put so much bother into it, that it
> would be easier to see exactly which projects you need to rebuild and and
> which you don't...
>
> Chris
>
>

Cool! Thanks.

Chris