Why is .net core allowing assembly access through project dependencies

Question

Consider this setup in .net framework projects/assemblies:

Now when I try to access Layer1 from Layer3, it won't allow me:

The type or namespace name 'Layer1' could not be found (are you missing a using directive or an assembly reference?)

This makes sense.

Now when I create the same setup in .net standard projects and a .net core console app, like so:

I am able to to this, and compile just fine:

Which makes no sense to me.

Is this by design? How do I prevent this behaviour?

And another one: https://stackoverflow.com/questions/42428571/transitive-references-in-net-core-1-1/42431299#42431299 — huysentruitw, Feb 11 '18 at 13:39
Right, so this is by design. Guess I googled for the wrong keywords.. — Flores, Feb 11 '18 at 13:41

score 3 · Accepted Answer · answered Feb 11 '18 at 13:56

3

So, turns out this is by design and the workaround is this:

  <ItemGroup>
      <ProjectReference Include="..\ClassLibraryA\ClassLibraryA.csproj" PrivateAssets="All" />  
  </ItemGroup>

1 Answers1