title: How does Microsoft.Extensions.Logging work for full .net framework?
body: <p>The article (<a href="https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-diagnostics-overview" rel="noreferrer">Monitor and diagnose Azure Service Fabric applications</a>) indicates following (please note text in bold):</p>
  
  <p><em>ASP.NET Core logging</em></p>
  
  <p><em>Choosing how to instrument your code can be difficult, if you chose poorly and have to reinstrument, you are revisiting and potentially destabilizing your code base. To reduce the risk, developers can choose an instrumentation library such as Microsoft.Extensions.Logging provided by ASP.NET Core. This provides an ILogger interface that allows the provider of your choice to be used while minimizing the impact to existing code. Another nice aspect of this is that the code can be used not only in .NET Core on Windows and Linux, but in the <strong>full .NET framework</strong> too, giving the ability to standardize your instrumentation code across .NET and .NET Core.</em></p>
  
  <p>How is this supposed to work because when I tried to add the extensions library (to my service fabric cluster application project that compiles to .net framework 4.5.2), it is attempting to bring down all asp.net core related binaries?</p>