You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
.NET Framework (Windows-only) or .NET Core: .NET 8.0
Environment (local platform and source/target platforms): SQL sdk project (sdk version 0.2.4-preview) /tp:Sql150 on Windows 11
Steps to Reproduce:
Create new SQL project for SQL-Server 2019: dotnet new sqlproj -tp Sql150
Write SQL-Script for CREATE ASSEMBLY containing your assembly as binary literal, e.g.: CREATE ASSEMBLY [TestCLR] AUTHORIZATION [dbo] FROM 0x4D5A90000300000...
Run: dotnet build
Build fails with "Build error SQL70557: This assembly is corrupt or not valid" pointing to your CREATE ASSEMBLY script.
For a cross check, executed CREATE ASSEMBLY script with SSME. Assembly gets imported flawless if appropriate conditions are met (CLR-support enabled, login for assemblies signing key created).
Also tried copying dll to $(IntermediateOutputPath) and $(OutputPath) and using assemblies name instead off binary literal. Leads to SQL70502: The assembly source is not valid. Only binary literals are allowed .
Steps to Reproduce:
Build fails with "Build error SQL70557: This assembly is corrupt or not valid" pointing to your CREATE ASSEMBLY script.
For a cross check, executed CREATE ASSEMBLY script with SSME. Assembly gets imported flawless if appropriate conditions are met (CLR-support enabled, login for assemblies signing key created).
Also tried copying dll to$(IntermediateOutputPath) and $ (OutputPath) and using assemblies name instead off binary literal. Leads to SQL70502: The assembly source is not valid. Only binary literals are allowed .
Did not test on prior versions of SDK.
Find sample-project attached. MySqlProj.zip
(DacFx/SqlPackage/SSMS/Azure Data Studio)
The text was updated successfully, but these errors were encountered: