Replies: 3 comments 2 replies
-
Compared with MySQL, PgSQL, Oracle and other driven frameworks, it is too radical |
Beta Was this translation helpful? Give feedback.
-
I think there's a misunderstanding here; .NET applications target either .NET Framework or modern .NET (Cone), rather than .NET Standard. Microsoft.Data.SqlClient still targets .NET Framework, so is usable from all .NET Framework applications.
FYI the .NET PostgreSQL driver - Npgsql - has done something much more radical, and entirely dropped support for .NET Framework in the latest version (9.0). In contrast, SqlClient still supports .NET Framework - just not via .NET Standard. |
Beta Was this translation helpful? Give feedback.
-
CentOS7 (GLIBC) is not supported since .NET8, so .NET7 is still used |
Beta Was this translation helpful? Give feedback.
-
I'm puzzled by the decision to drop support for .NET Standard in the 6.0 release. This change leaves anyone with a .NET application using .NET Standard in a bind. They are now forced to choose between the deprecated System.Data.SqlClient 4.9.0 or Microsoft.Data.SqlClient 5.2, which can't be upgraded or patched due to the lack of support for .NET Standard beyond that version. It's hard to believe that, despite .NET Framework and .NET Core being maintained concurrently, the connection between the two is gradually fading away.
Beta Was this translation helpful? Give feedback.
All reactions