How does a project find dlls that it uses - where do I put them?

[HONOREDANCESTOR]

I am using some dlls from a third party, and I am writing a
multiproject solution that is supposed to use them. So I copied the
dlls to a bin directory in one of the projects, but the project does
not find them when I compile it.
Where should I put the dlls? Should I use 'add / reference'?
Thanks,
HA

[Spam Catcher]

HO*************@yahoo.com wrote in news:f222fed1-6780-44f5-b336-
e0**********@e10g2000prf.googlegroups.com:

Should I use 'add / reference'?

Yes.

--

[Phill W.]

Trevor Benedict wrote:

and to explicitly copy the dll to the bin folder, right click on the
Referenced library and make sure the Copy Local is set to True.

Given that I've spent an inordinate amount of my time trying to get rid
of this "Copy Local" option, may I ask why you recommend this?

If I've built and distributed a "shared" assembly, I'd far rather it was
safely in the GAC, stored once and re-used all over the machine, rather
than having loads of [potentially incompatible] copies of it springing
up all over the place ...

Regards,
Phill W.

[Trevor Benedict]

Phill,
I did not mean it as a recommendation, an available option was highlighted.

What are the requirements for an assembly to reside in the GAC. Whenever you
wrap an assembly without a strong name you don't have an option.

Moreover, xcopy becomes easier when the files are in one location.

Regards,

Trevor Benedict
MCSD

"Phill W." <p-.-a-.-w-a-r-d-@-o-p-e-n-.-a-c-.-u-kwrote in message
news:fi**********@south.jnrs.ja.net...

Trevor Benedict wrote:

Given that I've spent an inordinate amount of my time trying to get rid of
this "Copy Local" option, may I ask why you recommend this?

If I've built and distributed a "shared" assembly, I'd far rather it was
safely in the GAC, stored once and re-used all over the machine, rather
than having loads of [potentially incompatible] copies of it springing up
all over the place ...

Regards,
Phill W.