[jira] [Commented] (LOG4NET-383) Log4Net.Error throws VerificationException - Operation could destabilize the runtime

2013-10-10 Thread Dominik Psenner (JIRA)

[ 
https://issues.apache.org/jira/browse/LOG4NET-383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13791306#comment-13791306
 ] 

Dominik Psenner commented on LOG4NET-383:
-

LOG4NET-318 was an issue where PEVerify complained about a security problem. I 
believe that alone would not cause the "destabilize the runtime"-exception but 
rather could cause a security or marshalling exception.

> 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

2013-10-10 Thread Stefan Bodewig (JIRA)

[ 
https://issues.apache.org/jira/browse/LOG4NET-383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13791283#comment-13791283
 ] 

Stefan Bodewig commented on LOG4NET-383:


LOG4NET-318 maybe?

> 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

2013-10-09 Thread Dominik Psenner (JIRA)

[ 
https://issues.apache.org/jira/browse/LOG4NET-383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13791228#comment-13791228
 ] 

Dominik Psenner commented on LOG4NET-383:
-

Interesting. We've changed nothing to fix this issue. Have you updated .NET or 
installed a windows update such that this issue was fixed by that? Does the 
issue come back if you downgrade to 1.2.11?

> 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

2013-10-09 Thread Brian Choi (JIRA)

[ 
https://issues.apache.org/jira/browse/LOG4NET-383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13790997#comment-13790997
 ] 

Brian Choi commented on LOG4NET-383:


Hi Dominik.

MS patch didn't fix this issue. However after upgrading to the latest log4net 
(from 1.2.11 to 1.2.12) Error() is working properly again.

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

2013-10-07 Thread Dominik Psenner (JIRA)

[ 
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] [Commented] (LOG4NET-383) Log4Net.Error throws VerificationException - Operation could destabilize the runtime

2013-10-07 Thread Brian Choi (JIRA)

[ 
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

2013-09-11 Thread Dominik Psenner (JIRA)

[ 
https://issues.apache.org/jira/browse/LOG4NET-383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13764210#comment-13764210
 ] 

Dominik Psenner commented on LOG4NET-383:
-

We were not yet able to reproduce this issue but if you were able to work out 
an example application or maybe even a NUnit test case showing the issue would 
be awesome!

> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (LOG4NET-383) Log4Net.Error throws VerificationException - Operation could destabilize the runtime

2013-09-11 Thread Chirayu Shishodiya (JIRA)

[ 
https://issues.apache.org/jira/browse/LOG4NET-383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13764192#comment-13764192
 ] 

Chirayu Shishodiya commented on LOG4NET-383:


We have a user who hit this too. Our application is MVC3 and runs in .NET 4. 
This is the stack trace he sent me:

VerificationException- Operation could destabilize the runtime. 
at log4net.Core.LogImpl.Error(Object message, Exception exception) 
at RedGate.Deploy.Portal.Application.DmController.OnException(ExceptionContext 
exceptionContext) 
at 
System.Web.Mvc.ControllerActionInvoker.InvokeExceptionFilters(ControllerContext 
controllerContext, IList`1 filters, Exception exception) 
at System.Web.Mvc.ControllerActionInvoker.InvokeAction(ControllerContext 
controllerContext, String actionName) 
at System.Web.Mvc.Controller.ExecuteCore() 
at System.Web.Mvc.ControllerBase.Execute(RequestContext requestContext) 
at 
System.Web.Mvc.MvcHandler.<>c__DisplayClass6.<>c__DisplayClassb.b__5()
 
at 
System.Web.Mvc.Async.AsyncResultWrapper.<>c__DisplayClass1.b__0()
 
at 
System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
 
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& 
completedSynchronously)

Have you guys reproduced this? Any help I can offer to reproduce this?

> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (LOG4NET-383) Log4Net.Error throws VerificationException - Operation could destabilize the runtime

2013-07-17 Thread Dominik Psenner (JIRA)

[ 
https://issues.apache.org/jira/browse/LOG4NET-383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13711007#comment-13711007
 ] 

Dominik Psenner commented on LOG4NET-383:
-

I'm wildly guessing that you are using a log4net version compiled for a 
different .NET framework version than your ASP.NET project does (i.e. log4net 
built against .NET 4.0 but your project is targeted to .NET 2.0). Can you 
verify this?

> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (LOG4NET-383) Log4Net.Error throws VerificationException - Operation could destabilize the runtime

2013-07-16 Thread Arun (JIRA)

[ 
https://issues.apache.org/jira/browse/LOG4NET-383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13710665#comment-13710665
 ] 

Arun commented on LOG4NET-383:
--

Here is the stack trace from a Test Application:

[VerificationException: Operation could destabilize the runtime.]
   log4net.Core.LogImpl.Error(Object message) +17
   Log4NetTest.WebForm2.Page_Load(Object sender, EventArgs e) in 
f:\CodeSamples\PortalTest\Log4NetTest\Log4NetTest\WebForm2.aspx.cs:13
   System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, 
Object t, EventArgs e) +25
   System.Web.UI.Control.LoadRecursive() +116
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, 
Boolean includeStagesAfterAsyncPoint) +2793

The line of code that throws this exception is :
catch(ex)
{
_log.Error("Exception caught", ex);
}

Whereas the following line works:
catch(ex)
{
_log.Debug("Error found", ex);

}

> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (LOG4NET-383) Log4Net.Error throws VerificationException - Operation could destabilize the runtime

2013-07-14 Thread Dominik Psenner (JIRA)

[ 
https://issues.apache.org/jira/browse/LOG4NET-383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13708264#comment-13708264
 ] 

Dominik Psenner commented on LOG4NET-383:
-

I'm not able to reproduce this. Would you please post a stacktrace showing 
where the exception is thrown?

> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira