What new or enhanced feature are you proposing? Strong naming the assembly.

What goal would this enhancement help you achieve? As is, it can not be linked into strong named projects without a custom re-compile with a strong name added. The key needn't be secure, just present so that the compile doesn't complain about a non-strong named assembly being linked in.

Issue 204 has been merged into this issue.

This is especially important for the nuget package as it is totally unexpected to have to do this

Strong naming is a big issue for NuGet as a whole. From what I understand, the NuGet team are going to put functionality in place to automatically strong name assemblies where necessary. See this thread for more info: http://nuget.codeplex.com/discussions/247827

Issue 241 has been merged into this issue.

Also critical for any (RELEASE) builds which are to be strongly named!

This issue is very closely related to Issue 79

Please sign it... It is easy (and I did it) the real problem is that Nuget Package is not signed so in cannot use from nuget as dependency and I have to create a custom package just because it is not signed...

For crying out cornflakes, Aziz, would you PLEASE just sign the assembly? How long has this been? Too long. What is your possible motivation for not signing it? It is dirt simple. It takes 2 seconds. Sheesh, you have Elmah in Nuget and it is unsigned? This is really weird. Please, Aziz, try to get to this. It just makes no sense. Please.

Issue 340 has been merged into this issue.

I am trying to set up an extension library within the MassTransit project (Service Bus) that uses Elmah logging. Without strong naming the assembly, I cannot get my changes into NuGet through their build system.

Would you please handle this ASAP?

Thanks, Todd

Why the problem still exists? Is that so hard add a Strong Name?

Issue 396 has been merged into this issue.

This issue has been migrated to: https://github.com/elmah/Elmah/issues/109 The conversation continues there. DO NOT post any further comments to the issue tracker on Google Code as it is shutting down. You can also just subscribe to the issue on GitHub to receive notifications of any further development.