Missing Type Microsoft.Data.SqlClient.SqlAuthenticationMethod - .NET Framework 4.8

[rozeboosje]

Describe the bug

Code snippet in VB.NET

`'

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`

Exception message: Could not load type 'Microsoft.Data.SqlClient.SqlAuthenticationMethod' from assembly 'Microsoft.Data.SqlClient, Version=7.0.0.0, Culture=neutral, PublicKeyToken=23ec7fc2d6eaa4a5'.
Stack trace:

To reproduce

The above may suffice to reproduce the issue?

Expected behavior

A clear and concise description of what you expected to happen.

Further technical details

Microsoft.Data.SqlClient version: 7.0.0
.NET target: (e.g. .NET Framework 4.8)
SQL Server version: (e.g. SQL Server 2022 - Azure SQL)
Operating system: n/a

Additional context

[rozeboosje]

I created a standalone project for .NET Framework 4.8 and installed nuget package Microsoft.Data.SqlClient 7.0.0 and I pasted in the above code. It then complained about the last two statements and I realised I also needed to add the nuget package for Microsoft.Sql.SqlManagementObjects - the latest version of that is 181.15.0 and once I did that it threw the exact same error. So it looks to me that SqlManagementObjects is not up to date on Microsoft.Data.SqlClient (yet?)

What should I do with that information?

[rozeboosje]

I cannot find a github page where I could alert its developers to this problem?

[rozeboosje]

Found it: microsoft/sqlmanagementobjects#218

[rozeboosje]

Please note: We're using SMO because our software needed to be able to process a large SQL script with statements separated by "GO" commands against Azure SQL databases. We would really prefer not to have to write code to "parse" such scripts into separate statements.

If there is a way to achieve this without using SMO, please let us know how.

[ErikEJ]

Given that 7.0.0 was released yesterday maybe give the ecosystem a little breating room to catch up?

Did you read the breaking changes docs?

Do you NEED 7.0.0 today?

[rozeboosje]

Thank you ErikEJ - yes I'm happy to wait for that and you're right, I don't need it today. I am hoping though that in the longer run I can keep all nuget packages up to date

[ErikEJ]

Did you add a reference to the new Azure package?

[rozeboosje]

Yes, thanks ErikEJ, but that made no difference. I'm a little unfamiliar with where to find information in these "github" places.... if there's a link to these "breaking changes" you mentioned, could you share it with me here?

[cheenamalhotra]

Do you experience any issue without SMO in a standalone VB.NET app?