You should have both projects in the same solution (.sln file) instead of
separate VS.NET instances and ensure that you are using a Project Reference
(there is a tab in the Add References dialog) from the Exe project to the
DLL project and not an .NET assembly reference to the compiled dll.

The CopyLocal=True property of the project reference will ensure that the
reference is up-to-date after each build.

--

Best regards,

Carlos J. Quintero

MZ-Tools: Productivity add-ins for Visual Studio .NET, VB6, VB5 and VBA
You can code, design and document much faster.
Free resources for add-in developers:
http://www.mztools.com

"ssg31415926" <newsjunkmail@gmail.com> escribió en el mensaje
news:1129890085.073002.289500@o13g2000cwo.googlegroups.com...
[quoted text, click to view]

In VS2003, I've got a .exe project which references a DLL written in a
separate project. I have two instances of VS open and e.g. add a
public method to the DLL and rebuild. It doesn't appear in the .exe
project unless I remove and re-add the reference. Is there any way to
do a quick 'refresh' of the reference so that the new method will
appear?