[
https://issues.apache.org/jira/browse/LOG4NET-398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14658748#comment-14658748
]
JOHN Alexander ZABROSKI edited comment on LOG4NET-398 at 8/5/15 7:47 PM:
-------------------------------------------------------------------------
What .NET version number did this problem occur on?
With the new RyuJIT optimization bugs becoming mainstream knowledge, I wonder
if we need to add a custom field to JIRA to track which release of .NET the
reporter is using.
Further, are you running .NET 4.6 with Optimization enabled?
was (Author: johnzabroski):
What .NET version number did this problem occur on?
With the new RyuJIT optimization bugs becoming mainstream knowledge, I wonder
if we need to add a custom field to JIRA to track which release of .NET the
reporter is using.
> 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)
