[
https://issues.apache.org/jira/browse/LOG4NET-398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15061999#comment-15061999
]
Dominik Psenner commented on LOG4NET-398:
-----------------------------------------
Only classes derived from MarshalByRefObj are allowed to cross application
domains. I'm still wondering why the ReadOnlyPropertiesDictionary crosses
application domains. A class should not travel between application domains "by
magic" as both application domains do not share the same memory and are
virtually two processes executing in one process (this really sounds strange,
yeah).
So long as the root cause is not found I do not think that this patch should be
applied.
> 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
> Attachments: log4net.zip
>
>
> 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)
