How to completely disable signed assemblies?

I have a VS.NET 2010 solution with multiple projects. I just added a new library project (the.library.assembly). A startup project is a website. When I launch the website, I get this error:

Failed to load file or assembly 'the.library.assembly' or one of its dependencies. A strong signature signature cannot be verified. Perhaps the assembly was changed, or it was signed with a delay, but not completely signed with the correct private key. (Exception from HRESULT: 0x80131045)

Where is it from? I have not used signed assemblies with other projects, and they work fine.

--- EDIT ---

Actually, I found that the subscription was collected. This was due to the issue of resolving the signed issue. I disabled this in the project properties and went through all the projects in the solution. They don’t sign anything. Now I get a build error:

Assembly generation failed -- Referenced assembly 'the.library.assembly' does not have a strong name. 

I thought that maybe this is due to the WCF service referenced by the library. I deleted the service and its associated code. Everything is built perfectly. I added the service back. Another good build. I added the code associated with the service back to the.library.assembly. Still building. Then I added the calls to the.library.assembly to the web application. This is when I get a build failure.

+3
source share
1 answer

I found entries that reference signing in the AssemblyInfo.cs web application. Commenting on this, a solution is allowed.

+1
source

All Articles