Replies: 1 comment
-
Hi @kefyru - the behavior you are observing is by design and actually desired. The Access to transitive dependencies can reinforce bad design practices by allowing breaking of layering of the intended architecture. All projects should declare their dependencies explicitly. The SDK projects opened access to transitive project references - but this was provided mainly for compiler and analyzers purposes. End user projects are not recommended to rely on and (ab)use the behavior (in fact - one can, and probably should - set More details on controling dependencies behavior can be found in our docs: https://github.com/dotnet/msbuild/blob/main/documentation/wiki/Controlling-Dependencies-Behavior.md |
Beta Was this translation helpful? Give feedback.
-
I have library
MyLib
:SomeUtil.dll
is .net assembly built with external tool.In
MyLib
i can access all members ofSomeUtil.dll
When i reference
MyLib
to another assembly, i have no access toSomeUtil.dll
.I can reference it manually, but is there any way to reference it automatically?
Beta Was this translation helpful? Give feedback.
All reactions