How to tell VS C# to stop coying ref assemblies locally

Hot Topic

Customize Add reference actions
How to make datagrid cell clickable
VS2005 Command Line Builds with nANT [build using Nant 0.85 ]
Help refactoring a method
Vista RTM can't open new socket.
How can I rename a file in C#?
enumerate the list of services associated with a Process in C#
documentcomplete event
Error when exporting to Excel
Reading AutoCad Files ! ! !

Visual C#

Custom #if Statement
memory stream to DB
VS 2005 crashes when launching "Add Reference" dialog
Mysql with c#
Modification for PDA devices...?
How do i create an assembly...
help required
Exception Error Display
Similar question.
How can I write a program that makes another program?

How to tell VS C# to stop coying ref assemblies locally

Hello,

I'm using VS2005 Pro Edition and my C# project is referencing an external assembly. The external assembly gets copied locally in my project folder when I build the project in debug mode. Also, the output library that the project builds is created twice: one copy in the project output folder (as set in my project) and another copy in the obj\Debug folder.

I really need to get rid of this behavior. Is there an option in VS2005 to avoid that

Thanks for your help,

-mab

Answer this question

How to tell VS C# to stop coying ref assemblies locally

  • JavaBoy

    Open the "References" node in Solution Explorer, select the reference to the external assembly. In the Properties window, set Copy Local to False.

  • SimonOng

    OK I see: <Private>False</Private>

    What about the output lib being copied in obj\Debug Is there also a similar XML tag for that

    Thanks

    -mab

  • Louis Y

    Well, seems to be a bug in VS then. There is no way I can avoid the output file duplication unless I set the project output path to .\obj\Debug which appears to be hard-coded somewhere in the settings ...
  • How to tell VS C# to stop coying ref assemblies locally
Answer this question