IT:AD:NET:Standard
Summary
NET Standard replaces IT:AD:NET:Portable Class Library (PCL) taking into account IT:AD:NET:Core development.
It's sort of the NET Core's equivalent to NET full framework's IT:AD:NET:HowTo:Base Class Library (BCL), adding in a bit (linq, xml, etc).
The key difference between IT:AD:NET:Portable Class Library (PCL) and IT:AD:NET:Standard is whereas IT:AD:NET:Portable Class Library (PCL) caused a different fork for each target, IT:AD:NET:Standard works using stack specific Type Forwarders, forwarding to a common base Standard implementation.
NET Standard: * is a set of APIs that all .NET platforms (.NET Framework, .NET Core, and Xamarin) have to implement. This unifies the .NET platforms and prevents future fragmentation. * For .NET Core, this will add many of the existing APIs that have been requested. * .NET Standard 2.0 includes a compatibility shim for .NET Framework binaries, significantly increasing the set of libraries that you can reference from your .NET Standard libraries. * will replace IT:AD:NET:Portable Class Library (PCL) as the tooling story for building multi-platform .NET libraries. * Scheduled for Q1 2017, in line with scheduled release of next version of IT:AD:Visual Studio, which is 7/3/20171).
Notes
- Advantages:
- Provides the definition of the minimum that various frameworks have to implement.
- Fixes the reality that porting from .NET to .NET Core was too painful. The API differences were too many. With a default .NET Standard base, porting is expected to be greatly simplified.
- Considerations:
- A side effect is to replace/retire IT:AD:NET:Portable Class Library (PCL).
- Really think of IT:AD:NET:Standard as the IT:AD:NET:Core equivalent to IT:AD:NET:HowTo:Base Class Library (BCL), and not IT:AD:NET:HowTo:Framework Class Library (FCL) (in other words, ASP.NET, etc. is not part of IT:AD:NET:Standard).
- Expect it on 7/3/20172)
