ELMAH's package isn't strongly signed with a pfx or snk file.

[GoogleCodeExporter]

ELMAH's NuGet package isn't strongly signed. This makes it annoying to use when 
you try to put it in another project that IS. It breaks the build.

Original issue reported on code.google.com by wforney@gmail.com on 3 Feb 2011 at 9:49

• Merged into: Strong name the assembly #109

[GoogleCodeExporter]

I think this is a dup of 109

Original comment by linden.k...@gmail.com on 17 Feb 2011 at 8:26

[GoogleCodeExporter]

Yes, it is, specifically for NuGet this is a big problem as the point of NuGet 
is to let you include packages in your other work. This prevents people from 
using the package on projects that are strongly signed.

Original comment by wforney@gmail.com on 17 Feb 2011 at 11:35

[GoogleCodeExporter]

Original comment by azizatif on 18 Feb 2011 at 12:30

• Changed state: Duplicate

[GoogleCodeExporter]

In this instance, I think this is a much bigger issue with NuGet than just 
relating to ELMAH. I suggest following this discussion to see where things are 
going with this one:

http://nuget.codeplex.com/discussions/247827

Original comment by jamesdriscoll71 on 1 Mar 2011 at 10:26