Proper use of shared references

[ljlevend]

I have a situation where project A references project B which references
project C, all of which are in the same solution. Project A is the Startup
solution. Also, I use a couple of third party dll's in the projects (lets
call them Ref.NET and Ref.COM). As you probably guessed by the names, one is
a .NET reference and the other is a COM reference.. Ref.NET is referenced by
all of the projects while Ref.COM is only referenced by projects B and C.

My question is what is the proper way to reference Ref.NET and Ref.COM?
Should I always use Copy Local = True, or is it better to use Copy Local =
False in some of the projects? Note that both dll’s default to Copy Local =
True when they are added to the projects, even though Ref.NET's Strong Name
property is True in the Properties window.

Thanks for any help.
Lance

[Phill. W]

"ljlevend" <lj******@nospam.nospam> wrote in message
news:13**********************************@microsof t.com...
.. . .

My question is what is the proper way to reference Ref.NET and
Ref.COM?
Should I always use Copy Local = True, or is it better to use Copy
Local = False in some of the projects?
Personally, I /avoid/ Copy Local whenever and wherever possible.
OK, so I lose the "dynamic updating" that a local assembly gets if
I ever "drop in" a new copy but, in my setup, that's not an issue.
Also, once Copy Local "takes hold", I've found it quite difficult to
"persuade" it to let go again, even if I do subsequently put things into
the GAC so they are global to the machine.
Note that both dll's default to Copy Local = True when they are
added to the projects, even though Ref.NET's Strong Name
property is True in the Properties window.

Strong Naming is only part of the Battle. You have to add the
assembly into the Global Assembly Cache before Copy Local finally
gives up trying to assimilate your Dll.

HTH,
Phill W.