In the latest versions of .net, did something change in the assembly dependencies?

Question

.NET

There is such a solution structure in Visual Studio:
Project1 (main project)
Project2
Project3
Project1 uses classes from Project2 , Project2 uses classes from Project3. Accordingly, Project1 must refer to Project2 , Project2 must refer to Project3.
A few years ago, on a similar structure, I noticed that the solution does not compile unless you add a reference to Project3 in Project1 (although the classes from Project3 are not directly used inside the class code from Project1).
Now I created a similar structure in Visual Studio 2017, NOT adding a reference to Project3 in Project1, built it - and it went wrong.
Can anyone explain: am I confusing something, or have I forgotten something, or have they really changed it?

Answer 1

It's always worked that way. Those. the reference to Project3 does not have to be in Project1.
Most likely your problem had a different cause. But it was treated by adding a link to Project3. Maybe that's why you thought so.