[
https://issues.apache.org/jira/browse/LOG4NET-398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14599324#comment-14599324
]
Lars Nellemann Nielsen commented on LOG4NET-398:
------------------------------------------------
I'm not certain, frankly i'm a bit amazed that this is even an issue
Ive attached a simple project, so you can reproduce
the executing console application has no references to log4net, it doesn't even
have any references to the other console applications as they are being loaded
and executed with
[AppDomain.ExecuteAssembly(String)|https://msdn.microsoft.com/en-us/library/sxx9f4c2%28v=vs.110%29.aspx]
i.e only by their path
Placing log4net.dll in the root of the executing console application is just
the same as placing it in GAC
> SerializationException after setting a LogicalThreadContext property
> --------------------------------------------------------------------
>
> Key: LOG4NET-398
> URL: https://issues.apache.org/jira/browse/LOG4NET-398
> Project: Log4net
> Issue Type: Task
> Components: Core
> Affects Versions: 1.2.12
> Environment: Visual Studio 2010
> Reporter: Thomas Meum
> Priority: Minor
> Labels: triaged
>
> I have found that accessing Page.Request.Url after setting a
> LogicalThreadContext property causes a SerializationException with the
> following message: Type is not resolved for member
> 'log4net.Util.PropertiesDictionary,log4net, Version=1.2.12.0,
> Culture=neutral, PublicKeyToken=669e0ddf0bb1aa2a'.
> I have been able to reproduce the problem on two different machines with the
> following steps:
> 1. Create a new ASP.NET Empty Web Application
> 2. Add a reference to log4net.dll
> 3. Add a new Web Form
> 4. Add the following code to Page_Load:
> log4net.LogicalThreadContext.Properties["Test"] = 1;
> Uri url = Request.Url;
> 5. Hit F5
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
