dotnet 8.0.100-preview.6.23330.14 error. about sqlprovider HOT 12 OPEN

Sounds pretty much underlying driver problem.

Could be related:
dotnet/SqlClient#1930

from sqlprovider.

Do you still have the issue?

I'm running on 8.0.100-rc.1.23463.5 and Microsoft.Data.SqlClient 5.1.1 and all works well.

from sqlprovider.

I'll check. :)

from sqlprovider.

Still have problems..
[]
let ResolutionPath = SOURCE_DIRECTORY + """\SqlProvider"""

type sql =
SqlDataProvider<DatabaseVendor=Common.DatabaseProviderTypes.MSSQLSERVER_DYNAMIC, ResolutionPath=ResolutionPath, ConnectionString=cs>

when i try to run dotnet build, i get this:

FS3033: The type provider 'FSharp.Data.Sql.SqlTypeProvider' reported an error: Unable to load one or more of the requested types.Could not load type 'SqlGuidCaster' from assembly 'Microsoft.Data.SqlClient, Version=5.0.0.0, Culture=neutral, PublicKeyToken=23ec7fc2d6eaa4a5' because it contains an object field at offset 0 that is incorrectly aligned or overlapped by a non-object field.Details: Could not load type 'SqlGuidCaster' from assembly 'Microsoft.Data.SqlClient, Version=5.0.0.0, Culture=neutral, PublicKeyToken=23ec7fc2d6eaa4a5' because it contains an object field at offset 0 that is incorrectly aligned or overlapped by a non-object field.Current execution platform: .NETCoreApp,Version=v6.0

FS3033: The type provider 'FSharp.Data.Sql.SqlTypeProvider' reported an error: Unable to load one or more of the requested types.Could not load type 'SqlGuidCaster' from assembly 'Microsoft.Data.SqlClient, Version=5.0.0.0, Culture=neutral, PublicKeyToken=23ec7fc2d6eaa4a5' because it contains an object field at offset 0 that is incorrectly aligned or overlapped by a non-object field.Details: Could not load type 'SqlGuidCaster' from assembly 'Microsoft.Data.SqlClient, Version=5.0.0.0, Culture=neutral, PublicKeyToken=23ec7fc2d6eaa4a5' because it contains an object field at offset 0 that is incorrectly aligned or overlapped by a non-object field.Current execution platform: .NETCoreApp,Version=v6.0

interestingly, no problems are showing in Neovim. no diagnostics. It's apparently fine there..

In summary...
(╯°□°）╯︵ ┻━┻

from sqlprovider.

and switching back to dotnet 7.0.401 has no problems with dotnet build.

from sqlprovider.

I'm also having this issue.
How can I bypass this issue?

from sqlprovider.

Oh, I was using the MSSQLSERVER_SSDT

from sqlprovider.

hi, can you try with 1.3.19 please, there should be a fix now.

from sqlprovider.

I'll have to try that, next week. thanks for working on it!

from sqlprovider.

hi, can you try with 1.3.16 please, there should be a fix now.

What does this version apply to... a package, an SDK? I'm using the following and still have this issue:

SDK 8.0.100-rc.2.23502.2
Microsoft.Data.SqlClient 5.1.2
CoreCLR Version: 8.0.23.47906 (on Azure App Service)
.NET Version: 8.0.0-rc.2.23479.6 (on Azure App Service)

from sqlprovider.

What does this version apply to... a package, an SDK?

I assume he meant the SqlProvider version of the nuget package: https://www.nuget.org/packages/SQLProvider/#versions-body-tab

I'm using the following and still have this issue

You missed specifying SqlProvider version.

from sqlprovider.

Just use the .Net 8 and the latest version. But more the question is are you using the MSSQL or MSSQL_DYNAMIC or MSSQL_SSDT

from sqlprovider.