System.Data: we should review differences with .NET Framework about standard HOT 11 CLOSED

@layer07 what issues exactly? By 2019 you mean this year? DbProviderFactories on .NET Framework relies on configuration to store provider registrations, and there was never public API to register factories. In .NET Core registration exist only in memory and the API to register provider factories is really needed to make the rest of the methods return something. We don’t have plans at this stage to add this API to .NET Framework.

from standard.

Also there are some things we added to core like DbColumn which are excluded because the don't exist in netfx461. This is a special case of it was supported on top of a older netstandard version but wasn't part of netstandard itself, we may need to take a closer look at such APIs all up for things we are folding into netstandard.

from standard.

we've haven't included DbProviderFactories for examples, which I think we should

What would it do in .NET Core?

from standard.

Related: #356.

from standard.

DbProviderFactories.RegisterFactory is indeed bringing a lot of issues (2019). I am unable to find any documentation on this. Ideally it would be agnostic between .NET and .netcore.

from standard.

Hi! @divega, Sorry, basically 99% of all the codes I've seem breaking between .netcore and .net is because of DbProviderFactories.RegisterFactory does not exist under .Net Framework. I am still confused why it does not exist on .Net Framework (for instance 4.7.2). But maybe I am not meant to understand it now.
Thank you for your time

from standard.

@divega outside of DbProviderFactories -- which we added -- are we missing anything critical? If not, let's close.

from standard.

@terrajobst I am not aware of any other System.Data classes or methods missing in .NET Standard 2.1 that exist in .NET Framework. I would prefer to double-check. Can you suggest any easy way to do a diff?

cc @roji in case he is aware of other cases.

from standard.

Of the top of my head, I'm not aware of anything (did a quick git log on the corefx src/System.Data.Common directory to confirm).

Unless I'm mistaken the new DbDataReader schema API, which was added for .NET Core 1.x (including DbColumn which is mentioned above), was already added to .NET Standard 2.0 so no problem there. Aside from that I don't think there are any leftovers.

Obviously there are several things we're adding to .NET Core 3.0 (and Standard 2.1), but I'm assuming those don't make it back into .NET Framework.

from standard.

Looking at https://docs.microsoft.com/en-us/dotnet/api/system.data?view=netstandard-2.1 vs https://docs.microsoft.com/en-us/dotnet/api/system.data?view=netframework-4.8 there are a few types in the latter that aren't listed in the former. (Sorry if I've misunderstood and that's not what you're actually asking about.)

• class DataRowComparer<TRow>
• class DataRowExtensions
• interface IExtendedDataRecord
• others (not an exhaustive list)

For System.Data.Common (https://docs.microsoft.com/en-us/dotnet/api/system.data.common?view=netstandard-2.1 vs https://docs.microsoft.com/en-us/dotnet/api/system.data.common?view=netframework-4.8) there's DataRecordInfo and various other types from System.Data.Entity.dll.

from standard.

Since this is just tracking doing the diff -- which we just did -- we can close this.

from standard.