Unit testing strongly named class library

260 Views Asked by At

I am writing some unit tests for a class library which is typically published as a nuget package internally. I have added a class library to the solution (which only has the one other class library project until now) and added references to NUnit and the project to be tested.

I added a very simple test which creates an instance of one of the classes and it fails immediately with this error:

Strong name signature could not be verified.  The assembly may have been
tampered with, or it was delay signed but not fully signed with the correct
private key.

The class library which provides the body of the nuget package code has a key.snk file and a CompanyNamePublic.snk file.

What do I need to do to be able to add unit tests to this solution?

0

There are 0 best solutions below