SMO 181.15.0 compatibility issue with Microsoft.Data.SqlClient 7.0.0 - .NET Framework 4.8

[rozeboosje]

    Dim sConnectionString As String

    sConnectionString = "Server=[server name here].database.windows.net;Database=[database name here];Application Name=[something];uid=[a QL username];pwd=[a SQL password];TrustServerCertificate=True;"

    Dim oCONSQL As Microsoft.Data.SqlClient.SqlConnection = Nothing  

    oCONSQL = New Microsoft.Data.SqlClient.SqlConnection(sConnectionString)  

    oCONSQL.Open()  

    If oCONSQL.State = ConnectionState.Open Then  

        Dim oCONServerConnection As Microsoft.SqlServer.Management.Common.ServerConnection = Nothing  

        oCONServerConnection = New Microsoft.SqlServer.Management.Common.ServerConnection(sqlConnection:=oCONSQL)

    End If

There is a new nuget package for Microsoft.Data.SqlClient - build 7.0.0 - This appears to be incompatible with your latest package 181.15.0

I need to ask you to liaise with that team to make sure we can keep both nuget packages up to date.

[rozeboosje]

See: dotnet/SqlClient#4064

[shueybubbles]

for net48/net472 you need to have some kind of binding redirect in place so the SMO DLLs that are expecting SqlClient 6 can load SqlClient 7. Does VB.net do that automatically?

[rozeboosje]

Hm. I thought it does but let me see what happens if I explicitly add one

[rozeboosje]

Yes it does:

<dependentAssembly> <assemblyIdentity name="Microsoft.Data.SqlClient" publicKeyToken="23ec7fc2d6eaa4a5" culture="neutral" /> <bindingRedirect oldVersion="0.0.0.0-7.0.0.0" newVersion="7.0.0.0" /> </dependentAssembly>

[ceisele-r]

This also happens to us. I could not solve it by adding a binding redirect so I think the only solution is to wait until Microsoft.SqlServer.SqlManagementObjects supports Microsoft.Data.SqlClient v7.

[rozeboosje]

Agreed. And I'm happy to do that. Keep us posted, though!

[last-Programmer]

we are also getting this error on IOS maui with .net10

[fredericDelaporte]

After upgrading Microsoft.Data.SqlClient to 7.0.0 in a C# .net10 project using SMO, we encountered the same issue.

System.TypeLoadException: Could not load type 'Microsoft.Data.SqlClient.SqlAuthenticationMethod' from assembly 'Microsoft.Data.SqlClient, Version=7.0.0.0, Culture=neutral, PublicKeyToken=23ec7fc2d6eaa4a5'.
   at Microsoft.SqlServer.Management.Common.ConnectionSettings.InitFromSqlConnection(SqlConnection sc)
   at Microsoft.SqlServer.Management.Common.ConnectionSettings.InitFromSqlConnection(SqlConnection sc)
   at Microsoft.SqlServer.Management.Common.ConnectionManager..ctor(SqlConnection sqlConnectionObject, IRenewableToken accessToken)
   at Microsoft.SqlServer.Management.Common.ServerConnection..ctor(SqlConnection sqlConnection, IRenewableToken accessToken)
   at Microsoft.SqlServer.Management.Common.ServerConnection..ctor(SqlConnection sqlConnection)

Downgrading the SQL Client to 6.1.4 in this project dodges the issue. (But now, we have inconsistent dependencies in our solution.)

[ceisele-r]

I'm actually a bit lost.
Is there anything to be fixed here in SMO?

Or was this fixed with dotnet/SqlClient#4067 which is already merged?

[SimonCropp]

ceisele-r the pr is merged, but the sqlclient nuget containing it has not been released.

[ceisele-r]

Simon Cropp (@SimonCropp) yeah but will that be enough or do we additionally have to wait for a fix/release of `Microsoft.SqlServer.SqlManagementObjects´? Otherwise this issue can be closed once the Nuget package of SqlClient is released.

[rozeboosje]

Sorry folks I am not ignoring this but I am currently ill.

As for the issue I suggest that we wait until the next nuget package for SqlClient is released and I'll try to run my code again. If the problem then "goes away" I'd be happy to see this issue closed. I will report back but it may not be the very day the next SqlClient nuget package is released, depending on my own recovery.

[rozeboosje]

I see there is a new build in nuget - 181.19.0

Can I use this with Microsoft.Data.SqlClient 6.1.4?
Would it allow me to upgrade to Microsoft.Data.SqlClient 7.0.0 and not experience this issue?

[rozeboosje]

Tried it with Microsoft.Data.SqlClient 6.1.4 and all the functionality I rely on is working normally
Tried it with Microsoft.Data.SqlClient 7.0.0 and still presenting the same problem

So this issue remains relevant to the latest build 181.19.0

[shueybubbles]

the fix is going to be in sqlclient 7.0.1 which will add type forwards for the types that moved from sqlclient.dll to the new dll