Migrate Dependencies from DotNetFramework to DotNetStandard
For simple model assemblies it is usually sufficient to just re-create as dotnet-standard and adjust the dependency references in the caller.
For more complex code we use branch-by-abstraction to provide a clear seam between the calling application and the dependency.
The task of writing the new dependency (supplier) may be made more complex by further dependencies.
For example in an assembly that depends on the Microsoft Dynamics SDK significant refactoring will be needed as this is not available in a dotnet-standard version because of underlying WCF dependencies. (see migrating-power-platform-clients-to-dotnetcore)