References in VS.Net 2003

[Urs Vogel]

Hi

I observed that my solutions frequently changes the location of references.
I have a number of shared DLLs in my solution, used by different
applications. When adding the reference in the IDE withing the project,
they're automatically set to Copy Local, and it looks OK in the beginning.
As soon as I recompile, it changes the directory of some references to the
local directory of the application. It doesn't do it with all references,
and I couldn't figure out a pattern of which references are changed. The
whole solution and its applications are dependent from these DLLs, which I
set in 'dependencies' within each project. When finally building the
solution, I have to very careful that the latest versions of my DLLs are
included. This is really dagnerous in terms of QA...

Any hints where this could come from, or what I could do about it?

Thanks for any hints, Urs

 

[Miha Markic [MVP C#]]

Hi Urs,

Did you check Project/Properties/Reference Paths - those matters.

 

[Urs Vogel]

Thanks Miha

There's been a path pointing to the applications directory, which was not
obviously required. After removing it, it didn't happen anymore.


Urs

Hi Urs,

Did you check Project/Properties/Reference Paths - those matters.

--
Miha Markic [MVP C#] - RightHand .NET consulting & development
miha at rthand com
www.rthand.com

Hi

I observed that my solutions frequently changes the location of
references. I have a number of shared DLLs in my solution, used by
different applications. When adding the reference in the IDE withing the
project, they're automatically set to Copy Local, and it looks OK in the
beginning. As soon as I recompile, it changes the directory of some
references to the local directory of the application. It doesn't do it
with all references, and I couldn't figure out a pattern of which
references are changed. The whole solution and its applications are
dependent from these DLLs, which I set in 'dependencies' within each
project. When finally building the solution, I have to very careful that
the latest versions of my DLLs are included. This is really dagnerous in
terms of QA...

Any hints where this could come from, or what I could do about it?

Thanks for any hints, Urs