Closed SiberaIndustries closed 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?
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?
Sure, since we know the cause, the fix can be applied to Microsoft.SqlSerever.SqlManagementObjects
as well.
Fixed in v161.46437.65 of the Microsoft.SqlServer.SqlManagementObjects
package.
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:
Additional information:
161.46041.41
and161.46367.54
ended up in the same result