In the latest versions .net something changed in the dependencies of the assemblies?

There is a structure of a solution in Visual Studio:

Project1 (main project)
Project2
Project3

Project1 uses the classes from Project2 , Project2 Project3 uses classes from. Appropriately, needs to reference Project1 in Project2 , Project2 needs to reference Project3.

A few years ago on a similar structure I noticed that the solution won't compile unless you add a reference to Project3 to Project1 (although the classes in Project3 are not directly yuzayutsya within the code of the classes from Project1).

Now I created the same structure in Visual Studio 2017 without adding a reference to Project3 to Project1, sbuilder and it was culdrose.

Can someone explain whether I confuse something, or forgot something, whether they really changed it?
June 3rd 19 at 19:21
1 answer
June 3rd 19 at 19:23
Always so worked. Ie reference to Project3 don't have to be in Project1.
Most likely your problem had another cause. But I was treated by adding a reference to Project3. Maybe that's why you thought so.

Find more questions by tags .NETAssembling projects