469,964 Members | 1,483 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,964 developers. It's quick & easy.

What reference should I add, Debug or Release?

VM
When I'm adding a reference to another project that is built as one of the
Projects in the Solution, should I add the dll in Debug or the one in
Release? I usually also do a batch build of everything (Release and Debug)
so I don't know if that would be a factor.
The reason I'm asking is that one of the projects that I'm adding to another
project as reference is not recognizing any of the new changes (new methods)
that I've made. I have to delete the reference and add it once again.
Sometimes (although it's happened only once), even if I delete the
reference, and rebuild the project (to add as a ref), and add the reference
again, it still doesn't know that I added several more methods to a class in
the project that's being referenced. In this rare case, The only way to fix
this is by erasing all copies of the dlls created in the solution directory
and rebuilding the whole thing again.

Thanks.
Nov 16 '05 #1
2 2958
VM wrote:
When I'm adding a reference to another project that is built as one of the
Projects in the Solution, should I add the dll in Debug or the one in
Release? I usually also do a batch build of everything (Release and Debug)
so I don't know if that would be a factor.
The reason I'm asking is that one of the projects that I'm adding to another
project as reference is not recognizing any of the new changes (new methods)
that I've made. I have to delete the reference and add it once again.
Sometimes (although it's happened only once), even if I delete the
reference, and rebuild the project (to add as a ref), and add the reference
again, it still doesn't know that I added several more methods to a class in
the project that's being referenced. In this rare case, The only way to fix
this is by erasing all copies of the dlls created in the solution directory
and rebuilding the whole thing again.


You should not add a reference to the DLL file, you should add a
reference to the Project itself (there's a tab on the dialog
specifically for project references). That way VS.NET will
automatically use the debug or release build of that dll depending on
the build that you're performing.

--
mikeb
Nov 16 '05 #2
VM
Thanks. I hadn't seen that Tab page.
"mikeb" <ma************@nospam.mailnull.com> wrote in message
news:Of**************@tk2msftngp13.phx.gbl...
VM wrote:
When I'm adding a reference to another project that is built as one of the Projects in the Solution, should I add the dll in Debug or the one in
Release? I usually also do a batch build of everything (Release and Debug) so I don't know if that would be a factor.
The reason I'm asking is that one of the projects that I'm adding to another project as reference is not recognizing any of the new changes (new methods) that I've made. I have to delete the reference and add it once again.
Sometimes (although it's happened only once), even if I delete the
reference, and rebuild the project (to add as a ref), and add the reference again, it still doesn't know that I added several more methods to a class in the project that's being referenced. In this rare case, The only way to fix this is by erasing all copies of the dlls created in the solution directory and rebuilding the whole thing again.


You should not add a reference to the DLL file, you should add a
reference to the Project itself (there's a tab on the dialog
specifically for project references). That way VS.NET will
automatically use the debug or release build of that dll depending on
the build that you're performing.

--
mikeb

Nov 16 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

26 posts views Thread by Lasse Edsvik | last post: by
reply views Thread by Todd H | last post: by
reply views Thread by Duncan Mole | last post: by
9 posts views Thread by dee | last post: by
3 posts views Thread by mosscliffe | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.