Brett,
Highlight the reference, and set the "Copy Local" property to false.
This should tell the IDE to not copy the dll locally and use that as a
reference (instead, pointing to your dll).
Of course, you probably will have to reload the project, or re-add the
dll if you compile the other dll and make changes.
In this case, you should really just add that project to your solution
and then set the reference to that project, instead of the dll itself.
Hope this helps.
--
- Nicholas Paldino [.NET/C# MVP]
-
mv*@spam.guard.caspershouse.com
"Brett Romero" <ac*****@cygen.com> wrote in message
news:11**********************@g43g2000cwa.googlegr oups.com...
I have a DLL "file" reference in my project. The DLL has been updated.
I recompile my project but it does not see the DLL updates. I remove
and add back the DLL. Now I can see the updates.
This is a random thing. Sometimes the updates come through without my
having to remove/add the DLL. I'm using VS 2003. Any ideas on why
this happens?
Thanks,
Brett