[jira] [Created] (LOG4NET-397) Conflicts due to new strong name key
Joe created LOG4NET-397: --- Summary: Conflicts due to new strong name key Key: LOG4NET-397 URL: https://issues.apache.org/jira/browse/LOG4NET-397 Project: Log4net Issue Type: Bug Reporter: Joe Consider an application that uses two third-party assemblies: - AssemblyA from Supplier A, compiled with log4net 1.2.10 (old strong-name key) - AssemblyB from Supplier B, compiled with log4net 1.2.11 (new strong-name key) How can I make these two assemblies co-exist and use the same version of log4net? Maybe I'm missing something obvious, but I can't see any way to do this: for example I obviously can't have both log4net assemblies in the same bin folder, as they have the same name. I'm obviously not the only one who thinks there's a problem, e.g. issue LOG4NET-342 refers to "... the strong name horror too". The comment on this issue: "... But if you need the old "strong name", you can simply use the "oldkey" binaries. I can't see how this is a horror, but of course I'm biased." doesn't seem to address the problem of conflicts. Also there are no guidelines for component suppliers as to which version to use, which increases the risk of conflicts. In the absence of explicit guidelines, I guess legacy components will have the old key, whereas new ones will tend to use the new key, since that is the only version available via NuGet. The only solution I can see is the following: - The "new key" assembly needs to have a different name from the "old key" assembly (e.g. log4net-2.dll). - Use Type forwarding to enable both versions to co-exist. E.g. you could supply a special log4net.dll signed with the old key that uses type forwarding to forward to log4net-2.dll signed with the new key. Or vice-versa. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (LOG4NET-383) Log4Net.Error throws VerificationException - Operation could destabilize the runtime
[ https://issues.apache.org/jira/browse/LOG4NET-383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13788681#comment-13788681 ] Brian Choi commented on LOG4NET-383: Hi Dominik. I am having this issue when I installed .net 4.5 runtime. Only happens for Error() not for Info(). Is there any plan to support 4.5 soon? http://elegantcode.com/2012/08/23/net-4-5-operation-could-destabilize-the-runtime-yikes/ Brian. > Log4Net.Error throws VerificationException - Operation could destabilize the > runtime > > > Key: LOG4NET-383 > URL: https://issues.apache.org/jira/browse/LOG4NET-383 > Project: Log4net > Issue Type: Bug >Affects Versions: 1.2.10, 1.2.11 > Environment: IIS 7.5 / Win 2008 R2 > .Net 4.0 > MVC3 and WCF applications >Reporter: Arun > > We are running into this issue when we log errors/fatal message using > log4net. > > System.Security.VerificationException: Operation could destabilize the > > runtime.at log4net.Core.LogImpl.Fatal(Object message, Exception > > exception) > Strangely this happens only when we log as Error/Fatal, Info and Debug > messages log perfectly fine. Because of this exception, the real exceptions > are getting masked and its making it very hard for us to debug in deployed > environments. > I have tried searching online but to no avail. Any help is appreciated. > Environment details: > IIS 7.5 / Win 2008 R2 > .Net 4.0 > MVC3 and WCF applications > Here is the logging configuration- > > > > > type="log4net.Config.Log4NetConfigurationSectionHandler, log4net"/> > > >type="log4net.Appender.RollingFileAppender"> > > > > > > > > > > > > > > > > > > > > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (LOG4NET-383) Log4Net.Error throws VerificationException - Operation could destabilize the runtime
[
https://issues.apache.org/jira/browse/LOG4NET-383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13788949#comment-13788949
]
Dominik Psenner commented on LOG4NET-383:
-
We have no plans for 4.5, but it will come sooner or later. Have you tried this
update on your 4.5 installation?
http://support.microsoft.com/kb/2748645
I'm quoting KB2748645:
{quote}Assume that you upgrade an earlier version of the .NET Framework to the
.NET Framework 4.5 on a computer. When you use some third-party controls, you
may receive a System.Security.VerificationException exception. This issue
occurs if the following conditions are true:
The third-party controls use the generic types.
The CLR verifier is enabled by declaring an assembly that is marked as
security-transparent.{quote}
> Log4Net.Error throws VerificationException - Operation could destabilize the
> runtime
>
>
> Key: LOG4NET-383
> URL: https://issues.apache.org/jira/browse/LOG4NET-383
> Project: Log4net
> Issue Type: Bug
>Affects Versions: 1.2.10, 1.2.11
> Environment: IIS 7.5 / Win 2008 R2
> .Net 4.0
> MVC3 and WCF applications
>Reporter: Arun
>
> We are running into this issue when we log errors/fatal message using
> log4net.
> > System.Security.VerificationException: Operation could destabilize the
> > runtime.at log4net.Core.LogImpl.Fatal(Object message, Exception
> > exception)
> Strangely this happens only when we log as Error/Fatal, Info and Debug
> messages log perfectly fine. Because of this exception, the real exceptions
> are getting masked and its making it very hard for us to debug in deployed
> environments.
> I have tried searching online but to no avail. Any help is appreciated.
> Environment details:
> IIS 7.5 / Win 2008 R2
> .Net 4.0
> MVC3 and WCF applications
> Here is the logging configuration-
>
>
>
>
> type="log4net.Config.Log4NetConfigurationSectionHandler, log4net"/>
>
>
>type="log4net.Appender.RollingFileAppender">
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Comment Edited] (LOG4NET-383) Log4Net.Error throws VerificationException - Operation could destabilize the runtime
[
https://issues.apache.org/jira/browse/LOG4NET-383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13788949#comment-13788949
]
Dominik Psenner edited comment on LOG4NET-383 at 10/8/13 6:13 AM:
--
We have no plans for 4.5, but it will come sooner or later. Have you tried this
update on your 4.5 installation?
http://support.microsoft.com/kb/2748645
I'm quoting KB2748645:
{quote}Assume that you upgrade an earlier version of the .NET Framework to the
.NET Framework 4.5 on a computer. When you use some third-party controls, you
may receive a System.Security.VerificationException exception. This issue
occurs if the following conditions are true:
The third-party controls use the generic types.
The CLR verifier is enabled by declaring an assembly that is marked as
security-transparent.{quote}
Let us know if the installation of this KB fixes this issue. I can then look
towards updating the FAQ or troubleshooting section.
was (Author: nachbarslumpi):
We have no plans for 4.5, but it will come sooner or later. Have you tried this
update on your 4.5 installation?
http://support.microsoft.com/kb/2748645
I'm quoting KB2748645:
{quote}Assume that you upgrade an earlier version of the .NET Framework to the
.NET Framework 4.5 on a computer. When you use some third-party controls, you
may receive a System.Security.VerificationException exception. This issue
occurs if the following conditions are true:
The third-party controls use the generic types.
The CLR verifier is enabled by declaring an assembly that is marked as
security-transparent.{quote}
> Log4Net.Error throws VerificationException - Operation could destabilize the
> runtime
>
>
> Key: LOG4NET-383
> URL: https://issues.apache.org/jira/browse/LOG4NET-383
> Project: Log4net
> Issue Type: Bug
>Affects Versions: 1.2.10, 1.2.11
> Environment: IIS 7.5 / Win 2008 R2
> .Net 4.0
> MVC3 and WCF applications
>Reporter: Arun
>
> We are running into this issue when we log errors/fatal message using
> log4net.
> > System.Security.VerificationException: Operation could destabilize the
> > runtime.at log4net.Core.LogImpl.Fatal(Object message, Exception
> > exception)
> Strangely this happens only when we log as Error/Fatal, Info and Debug
> messages log perfectly fine. Because of this exception, the real exceptions
> are getting masked and its making it very hard for us to debug in deployed
> environments.
> I have tried searching online but to no avail. Any help is appreciated.
> Environment details:
> IIS 7.5 / Win 2008 R2
> .Net 4.0
> MVC3 and WCF applications
> Here is the logging configuration-
>
>
>
>
> type="log4net.Config.Log4NetConfigurationSectionHandler, log4net"/>
>
>
>type="log4net.Appender.RollingFileAppender">
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
--
This message was sent by Atlassian JIRA
(v6.1#6144)
