0

I have a .NET Core 2 solution with a number of projects.

I'm reorganising some code and have run into a very odd scenario. My API project had a reference to a library containing a class called IMyService.

This reference has been removed but the project can still "see" the IMyervice interface. The API does have a reference to a project that in turn does reference the IMyService project.

In "normal" .NET land I'd expect a compiler error given the scenario above. Why is the .NET Core API project still able to see a class in a project it doesn't directly reference?

Jammer
  • 9,969
  • 11
  • 68
  • 115
  • 1
    Transitive references, basically. (And boy do they make everything simpler.) I'm not adding an answer as there's a duplicate question that I'll try to find now. – Jon Skeet Mar 27 '18 at 11:03
  • Wow, OK. Never encountered them before, time to learn a new thing! – Jammer Mar 27 '18 at 11:06

0 Answers0