DLL administration

Posted by carlos on Stack Overflow See other posts from Stack Overflow or by carlos
Published on 2010-05-18T02:47:10Z Indexed on 2010/05/18 2:50 UTC
Read the original article Hit count: 255

Filed under:
|
|

I build some dlls to be used in a big application, and have a team working in the dlls heart of the application and another team working in the gui, but i am having a problems in the deployment of the dll's when a change is done, because the gui team needs or copy the new dll to the project folder, or delete the old reference and add the new one. Is there a best practice to deal with this problem?

I am using Visual Studio 2008 and devoloping int VB and C#

Thanks !!!

© Stack Overflow or respective owner

Related posts about vb

Related posts about .NET