Re: VS 2005 automatically deleting dlls?

Thomas Sun – MSFT — Fri, 31 Oct 2008 06:20:24 GMT

Hi,

If we add reference to other assemblies that are in the same solution, we can set Project Dependences (http://msdn.microsoft.com/en-us/library/zk4ahe0t%28VS.80%29.aspx) to make sure refered project is compiled before the project we add reference to.

I look forward to hearing from you.

VS 2005 automatically deleting dlls?

Flintronics — Wed, 29 Oct 2008 18:13:05 GMT

Hello,

I have three projects (A, B and C) in one solution. B is the main start-up project and A and C are referenced by it and it is setup so the A.dll and C.dll are copied to B's bin folder. When i build the solution, A.dll is created in it's bin folder (as expected) and the same version is created in the B's bin folder along with the others.

Now this is a vb project and contains some methods. When i run the project, the A.dll file exists in B's bin folder, but only until some methods are executed. The A.dll is deleted from B's bin folder before the program finishes and the next method fails because it can't find the file:

"Could not load file or assembly '*****, Version=1.0.****.****, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified."

Why is this happening? Why don't the A.dll file stay in the B's bin folder until the application exits? Is there an option that i can choose that won't delete the A.dll files? Thank you for your help.

Visual Studio 2005

Re: VS 2005 automatically deleting dlls?

VS 2005 automatically deleting dlls?