References in VS.Net 2003
From: Urs Vogel (uvogel_at_msn.com)
Date: 10/06/04
- Next message: James Curran: "Re: Iframes in aspx page."
- Previous message: Peder Y: "Movable controls at runtime..."
- Next in thread: Miha Markic [MVP C#]: "Re: References in VS.Net 2003"
- Reply: Miha Markic [MVP C#]: "Re: References in VS.Net 2003"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 6 Oct 2004 18:04:14 +0200
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
- Next message: James Curran: "Re: Iframes in aspx page."
- Previous message: Peder Y: "Movable controls at runtime..."
- Next in thread: Miha Markic [MVP C#]: "Re: References in VS.Net 2003"
- Reply: Miha Markic [MVP C#]: "Re: References in VS.Net 2003"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|