Missing System.String.Replace definitions in .NetStandard 2.0

[YohanSciubukgian]

From what I have understand, .Net Core 2.0 is an implementation of .Net Standard 2.0 .
However I'm facing an issue when I'm trying to move my code from a .Net Core 2.0 project to a .Net Standard 2.0 project with the following message :

No overload for method 'Replace' takes 3 arguments

.Net Standard 2.0 references the following methods :

• System.String.Replace(String, String);
• System.String.Replace(char, char);
  https://docs.microsoft.com/fr-fr/dotnet/api/?view=netstandard-2.0&term=string.replace

In another side, .Net Core 2.0 implements the following methods :

• System.String.Replace(String, String, bool, CultureInfo);
• System.String.Replace(String, String, StringComparison);
• System.String.Replace(String, String);
• System.String.Replace(char, char);
  https://docs.microsoft.com/fr-fr/dotnet/api/?view=netcore-2.0&term=string.replace

Is it possible to add these missing definitions to the next version of .NetStandard ?

[jnm2]

From what I have understand, .Net Core 2.0 is an implementation of .Net Standard 2.0 .

Yes, this means .NET Core APIs include .NET Standard 2.0 APIs, but not the other way around.

I have similar questions about many .NET Core APIs that I want to use both in .NET Standard and .NET Framework, so I will wait for the answer to your question with interest.

[svick]

For the record, those overloads were added to .Net Core in https://github.com/dotnet/corefx/issues/1271.

I'm not sure how exactly is the evolution of .Net Standard after 2.0 going to look like. Some hints from the documentation:

Moving forward, we want to open up .NET Standard to be driven by the .NET Standard review board. The board is comprised of implementers of .NET.

The idea being that the standard doesn't drive new APIs: rather, the work of the standard body is to decide which of the APIs available on some .NET platforms should be available on all .NET platform and thus be added to the standard. In other words, the innovation happens in the context of a particular .NET platform and standardization follows afterwards.

This makes it sound like just because an API was added to .Net Core (where most of innovation is happening now) does not mean it will automatically be added to .Net Standard.

I haven't heard anything concrete about the next version of .Net Standard, so I don't think it's going to happen in the next 6 months or so.

[jnm2]

This makes it sound like just because an API was added to .Net Core (where most of innovation is happening now) does not mean it will automatically be added to .Net Standard.

I hope not; but I do hope that there will be a structured way for us to request APIs. Perhaps we can open request issues in this repo and upvote them? Whatever the mechanism, it would be good if it was centralized in an open place.

[YohanSciubukgian]

This makes it sound like just because an API was added to .Net Core (where most of innovation is happening now) does not mean it will automatically be added to .Net Standard.

I though that .NetStandard referenced everything from .NetCore.
It seems fair, between .NetFramework & .NetCore, to not include only .NetStandard references in order to let the possiblity to .NetCore to go further.
But the lack of references might impact other implementations like Mono, Xamarin or UWP.
https://docs.microsoft.com/en-us/dotnet/standard/net-standard

In my case, I'll keep working with .NetCore instead of .NetStandard for my projects.
Thanks for details.