Skip to content

Instantly share code, notes, and snippets.

@tirolo
Created May 26, 2016 05:56
Show Gist options
  • Save tirolo/38319086ffcea42f9cf8946383b96526 to your computer and use it in GitHub Desktop.
Save tirolo/38319086ffcea42f9cf8946383b96526 to your computer and use it in GitHub Desktop.
Can someone link me to some facts about this API surface thing people were getting hot and bothered about earlier?

As per this comment: https://aspnetcore.slack.com/archives/general/p1464241815020472

As in: https://aspnetcore.slack.com/archives/general/p1464211494017795

Immo Landwerth (https://aspnetcore.slack.com/team/terrajobst) OK, first let me outline the general approach. As Miguel mentioned on Twitter, our goal is bring back more APIs to .NET Core. The general direction is:

  1. We're committed to a 100% source and binary compatibility with the subset of mscorlib and friends that are also exposed in Xamarin.
  2. We'll try to keep our implementation as factored as possible, without compromising (1).
  3. We'll have type forwarders from mscorlib and friends to our implementations (CoreCLR and CoreRT).
  4. We'll continue to support PCLs (mscorlib based as well as System.Runtime based).
  5. We're thinking about whether we should continue to base our library story on System.Runtime (i.e. contracts) or whether we'll be moving to mscorlib

here's the start of the day - https://aspnetcore.slack.com/archives/general/p1464210218017770

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment