search

qanuj / elmah

Automatically exported from code.google.com/p/elmah
0 stars 0 forks source link

Strong name the assembly #109

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
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.

Original issue reported on code.google.com by BrennanA...@gmail.com on 1 Jun 2009 at 2:42

GoogleCodeExporter commented 9 years ago 
Issue 204 has been merged into this issue.

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

GoogleCodeExporter commented 9 years ago 
This is especially important for the nuget package as it is totally unexpected 
to have to do this

Original comment by steelepr...@gmail.com on 4 May 2011 at 7:08

GoogleCodeExporter commented 9 years ago 
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

Original comment by jamesdriscoll71 on 5 May 2011 at 7:06

GoogleCodeExporter commented 9 years ago 
Issue 241 has been merged into this issue.

Original comment by jamesdriscoll71 on 22 Jul 2011 at 3:44

GoogleCodeExporter commented 9 years ago 
Also critical for any (RELEASE) builds which are to be strongly named!

Original comment by brickey....@gmail.com on 25 Jul 2011 at 1:36

GoogleCodeExporter commented 9 years ago 
This issue is very closely related to Issue 79

Original comment by c0bra99 on 28 Jul 2011 at 2:58

GoogleCodeExporter commented 9 years ago 
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...

Original comment by manudear...@gmail.com on 11 Feb 2013 at 10:10

GoogleCodeExporter commented 9 years ago 
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.

Original comment by mkamo...@gmail.com on 13 Feb 2013 at 9:06

GoogleCodeExporter commented 9 years ago 
Issue 340 has been merged into this issue.

Original comment by azizatif on 14 Aug 2013 at 6:17

GoogleCodeExporter commented 9 years ago 
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

Original comment by t...@meinershagen.net on 30 Sep 2013 at 5:01

GoogleCodeExporter commented 9 years ago 
Why the problem still exists?  Is that so hard add a Strong Name?

Original comment by huangjin...@gmail.com on 2 Nov 2014 at 12:45

GoogleCodeExporter commented 9 years ago 
Issue 396 has been merged into this issue.

Original comment by azizatif on 2 Aug 2015 at 9:17

GoogleCodeExporter commented 9 years ago 
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.

Original comment by azizatif on 25 Aug 2015 at 8:17