G
Guest
In a case you have Project/Assembly A references Project/Assembly B which
References Project/Assembly C.
Let's say Project A needs be and references it directly. Unknown to A, B
needs project C's assembly but it uses C's assembly dynamically (Load
Assembly).
Even with copy Local set on all references Project A when built will get
project B's output but not project C's.
This is from what I hear due to an "enhancement" in VS2005, that if a
reference is not directly used it is not copied (even regardless of copy
local setting).
Some would say a work around to this is to add C's reference to A. We would
call that a hack, as we don't want Project A to have to directly know about
project C.
Is there some workaround that we can revert back to the old way for
references? Is this a bug in VS2005 or was this supposed to be a feature.
You wouldn't think that the project should ignore the copy local flag.
Thanks
References Project/Assembly C.
Let's say Project A needs be and references it directly. Unknown to A, B
needs project C's assembly but it uses C's assembly dynamically (Load
Assembly).
Even with copy Local set on all references Project A when built will get
project B's output but not project C's.
This is from what I hear due to an "enhancement" in VS2005, that if a
reference is not directly used it is not copied (even regardless of copy
local setting).
Some would say a work around to this is to add C's reference to A. We would
call that a hack, as we don't want Project A to have to directly know about
project C.
Is there some workaround that we can revert back to the old way for
references? Is this a bug in VS2005 or was this supposed to be a feature.
You wouldn't think that the project should ignore the copy local flag.
Thanks