I'm still getting to grips with .Net Standard vs .Net Core after many years of development ASP.NET Framework. I have set up a new Web Api "app" which targets netcoreapp3.1
framework along with a middle-tier/Business Logic ClassLib and Data Access ClassLib, both of which target .Net Standard for maximum future compatibility. However, I can't seem to use ISystemClock
from the Microsoft.AspNetCore.Authentication
namespace in the .Net Standard classlibs!
From reading this SO question, I believe this might be because netstandard2.0
might not implement Microsoft.AspNetCore.App
framework. Is this correct?
If it doesn't, should I:
Provide my own
IMySystemClock
interface in my class libraries which the "app" itself can implement a trivial concrete class for?; orChange my class middle and data access tiers to
netcoreapp3.1
framework (seems over kill and restrictive to do this)?Something else? Maybe I am missing the point of .Net Standard`?
A service (like ISystemClock
) to provide the current (real or mock) time seems quite a fundamental service so I'm unsure why it's not appearing in .net standard framework?
Thanks BloodBaz