Version 0.11.7.0 Nest.Signed.dll and Nest.Connection.Thrift.Signed.dll are only delay-signed by a public key. If test Nest.Signed on a clean machine, you will get an error "Strong name signature could not be verified" Very similar to http://aspnetwebstack.codeplex.com/discussions/444111 Delay-signing is not enough for production. For now users must skip strong name verification on theirs machines to work with Nest.Signed. Please re-sign Nest.Signed by a full key (public+private). This will fix the problem. Signing dll by a full key will not compromise this key.