dotnet / standard

This repo is building the .NET Standard
3.07k stars 430 forks source link

Strong name signature not valid #1789

Closed SiberaIndustries closed 3 years ago

SiberaIndustries commented 3 years ago

Since I've ported a ClickOnce application from .NET Framework 4.6.1 to .NET Standard 2.0, the message "Strong assembly name signature not valid for Microsoft.SqlServer.Assessment.Types.dll" appears when trying to install or update the application. So the next step was to verify the assembly strong name by using the Strong Name Tool to make sure, that everything is fine, but:

> sn.exe -v Microsoft.SqlServer.Assessment.Types.dll

Microsoft (R) .NET Framework Strong Name Utility Version 4.0.30319.0
Copyright (c) Microsoft Corporation. All rights reserved.

Microsoft.SqlServer.Assessment.Types.dll is a delay-signed or test-signed assembly

Additional information:

markingmyname commented 3 years ago

assign: @alexprotsenko

aguzev commented 3 years ago

Thank you for this feedback! Please, update Microsoft.SqlServer.Assessment.Authoring package reference in the application to the latest version. Did this work?

SiberaIndustries commented 3 years ago

Your solution works, thanks!

Will this issue be fixed in future versions of the Microsoft.SqlServer.SqlManagementObjects package or do I have to make sure that the correct version of Microsoft.SqlServer.Assessment.Authoring is used?

aguzev commented 3 years ago

Sure, since we know the cause, the fix can be applied to Microsoft.SqlSerever.SqlManagementObjects as well.

aguzev commented 3 years ago

Fixed in v161.46437.65 of the Microsoft.SqlServer.SqlManagementObjects package.