logging-log4net-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LOG4NET-467) Is .NET Core, will be supported in the near future, or not
Date Wed, 30 Nov 2016 01:51:59 GMT

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

ASF GitHub Bot commented on LOG4NET-467:

Github user SeanSnyders commented on the issue:

    @bodewig I've downloaded[ your 2.0.6 version from myget ](https://www.myget.org/feed/log4net-test/package/nuget/log4net
)but get an exception thrown during init of my logger in a NetCoreApp 1.1.0 application targeting
    Now, I'm a bit new to .Net Core, but my same code runs fine using latest 2.0.5 on .Net
    Any chance of getting a `.pdb` of 2.0.6 so I can dig a bit deeper into where the exception
occur with a sensible stack trace?
    At a high level, I get these:
    in my code on line 176  here:
    If I add the dependency of `System.Collections.NonGeneric 4.3.0` to my `project.json`,
I still get an exception of:
    Is the nuget package for 2.0.6 specifying all the dependencies? What am I missing here?

> Is .NET Core, will be supported in the near future, or not
> ----------------------------------------------------------
>                 Key: LOG4NET-467
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-467
>             Project: Log4net
>          Issue Type: New Feature
>          Components: Core
>    Affects Versions: 1.2.13
>            Reporter: san kan
>              Labels: features
>             Fix For: 2.0.6
>         Attachments: LOG4NET-467.patch
> As you know, ms is moving heavily toward .Net core:
> https://github.com/dotnet/core
> so, is there a road map for making a version that supports it?
> and i noticed that log4net, has not been updated for 2 years.
> so is it maintained, or being forgotten?

This message was sent by Atlassian JIRA

View raw message