Stupid automatic assembly copy problem in Visual Studio 2008 - WTH am I doing wrong?

Posted by Dave on Stack Overflow See other posts from Stack Overflow or by Dave
Published on 2010-04-07T20:38:15Z Indexed on 2010/04/07 20:43 UTC
Read the original article Hit count: 159

My lazier side has apparently gotten the best of me. When I started to develop with .NET under VS2008 recently, I was very happy to see that all of the dependencies automagically got copied to my application's bin/debug folder upon compilation. This is fantastic. I never even bothered to look into how / why this is done.

Yesterday, I decided to make another plugin very similar to an existing one, so I literally copied the folder and all of project files, then renamed the folder and manually edited the project files and file references. I also changed the assembly's GUID.

Everything builds fine, but this particular assembly is never copied into my application's bin/debug folder. It is marked as a dependency of my app as well.

What did I miss here?

© Stack Overflow or respective owner

Related posts about visual-studio-2008

Related posts about copy