Closed dhutchins closed 2 years ago
You should be able to easily work around this by testing the assembly in project which is NOT strong named itself. If testing within existing strong-named code-base, you could just turn off strong naming for calling assembly for testing purposes. For example, by setting; <SignAssembly>False</SignAssembly>
in project file.
Since a workaround is available and strong naming of assembly is not related to the properties of specific feature being previewed, then it is no blocker going forward and I wouldn't be surprised if this was not addressed for this preview on the dll-side.
The API is available in https://www.nuget.org/packages/Microsoft.Azure.Cosmos/3.25.0-preview which has a signed Microsoft.Azure.Cosmos.Client.dll assembly.
Created a small console application and attempted to run a test. I downloaded the nuget package for this test. Receiving:
Could not load file or assembly 'Microsoft.Azure.Cosmos.Client, Version=3.15.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. Strong name validation failed. (Exception from HRESULT: 0x8013141A)
Running the command "sn -vf Microsoft.Azure.Cosmos.Client.dll", produces:
Microsoft (R) .NET Framework Strong Name Utility Version 4.0.30319.0 Copyright (c) Microsoft Corporation. All rights reserved.
Microsoft.Azure.Cosmos.Client.dll is a delay-signed or test-signed assembly
Any help would be appreciated.