-
Notifications
You must be signed in to change notification settings - Fork 146
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dotnet 8.0.100-preview.6.23330.14 error. #800
Comments
Sounds pretty much underlying driver problem. Could be related: |
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. |
I'll check. :) |
Still have problems.. type sql = 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... |
and switching back to dotnet 7.0.401 has no problems with dotnet build. |
I'm also having this issue. |
Oh, I was using the MSSQLSERVER_SSDT |
hi, can you try with 1.3.19 please, there should be a fix now. |
I'll have to try that, next week. thanks for working on it! |
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 |
I assume he meant the SqlProvider version of the nuget package: https://www.nuget.org/packages/SQLProvider/#versions-body-tab
You missed specifying SqlProvider version. |
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 |
Describe the bug
when I try to build with dotnet 8.0.100-preview.6.23330.14 sdk i get this error:
The type provider 'FSharp.Data.Sql.SqlTypeProvider' reported an error: Un
able 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, PublicKeyTo
ken=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 'SqlGu
idCaster' 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
To Reproduce
Steps to reproduce the behavior:
have a dotnet 8 sdk project.
use mssql
try to build
Expected behavior
i expect it to build
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context
None
The text was updated successfully, but these errors were encountered: