2
votes

Update 2015-11-17

It seems that vNext assemblies (Microsoft.AspNet) are now signed (have strong names).

Check the following thread on GitHub:

Assemblies are now strong named #109


I want to create a digital signed assembly, which will use types implemented in one of the vNext assemblies. At this moment, vNext assemblies do not have a strong name attribute. As a result, the following error occurs while building a solution:

"Assembly generation failed -- Referenced assembly 'Microsoft.AspNet.Http' does not have a strong name"

Is this behavior a known issue (for example, related to the VS2015 CTP)? Is it going to be changed in the future? What is the recommended way to proceed?

1
Though I answered a specific question below, it might be helpful to understand why you want to strong-name sign a DLL to begin with.Eilon

1 Answers

6
votes

Update 2015-11-17

As noted by Mikhail, nearly all the assemblies that are part of DNX 1, ASP.NET 5, and EF 7 have strong-name signatures.

They all use a private key that is checked in to the repo, so anyone can build the same DLLs with the same strong-name key. No "delay sign" or "test sign" process.


Original post 2015-02-11

There are no current plans to strong-name sign all the DLLs in ASP.NET 5. (Source: I work on the project.)

And because strong-name are "viral" (a strong-name signed assembly must reference only other strong-name signed assemblies), that means you cannot strong-name any assembly that depends on ASP.NET 5.