[GitHub] log4net issue #16: (LOG4NET-467) .NET Core support

Github user robcube commented on the issue: https://github.com/apache/log4net/pull/16 Bingo, found the culprit: ``` ``` Changed it to ` ` Problem solved. :-) I guess XmlLayoutSchemaLog4j isn't quite there yet. --- If your

[GitHub] log4net issue #16: (LOG4NET-467) .NET Core support

Github user NachbarsLumpi commented on the issue: https://github.com/apache/log4net/pull/16 I guess that writing xml tags that include a namespace results in the observed exception. Few people use xml layouts for logs, so this might be a regression or an incompatibility that shows

[GitHub] log4net issue #16: (LOG4NET-467) .NET Core support

Github user robcube commented on the issue: https://github.com/apache/log4net/pull/16 Getting a weird error using .net core 1.1: ``` var logRepository = LogManager.GetRepository(Assembly.GetEntryAssembly()); XmlConfigurator.ConfigureAndWatch(logRepository, new

[GitHub] log4net issue #16: (LOG4NET-467) .NET Core support

Github user bodewig commented on the issue: https://github.com/apache/log4net/pull/16 I've spelled out https://github.com/apache/log4net/blob/6e8c0db1407a398fa64d72f89cf6b460ad209808/src/site/xdoc/release/framework-support.xml#L578 which will become visible at

[GitHub] log4net issue #16: (LOG4NET-467) .NET Core support

Github user SeanSnyders commented on the issue: https://github.com/apache/log4net/pull/16 Right, okay. Yes a a list of things not working would be great. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your

[GitHub] log4net issue #16: (LOG4NET-467) .NET Core support

Github user bodewig commented on the issue: https://github.com/apache/log4net/pull/16 Yes, that seems to be expected as `src/Util/PatternStringConverters/EnvironmentFolderPathPatternConverter` is among the excludes in

[GitHub] log4net issue #16: (LOG4NET-467) .NET Core support

Github user SeanSnyders commented on the issue: https://github.com/apache/log4net/pull/16 @bodewig I can confirm that the dependencies now seem to be solved, thanks. But I get that the my log file pattern does not seem to work using the `envFolderPath`

[GitHub] log4net issue #16: (LOG4NET-467) .NET Core support

Github user SeanSnyders commented on the issue: https://github.com/apache/log4net/pull/16 @bodewig Great, I'll try it again. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature

[GitHub] log4net issue #16: (LOG4NET-467) .NET Core support

Github user bodewig commented on the issue: https://github.com/apache/log4net/pull/16 @SeanSnyders I've updated the package at https://www.myget.org/feed/log4net-test/package/nuget/log4net (overwritten the original one) --- If your project is set up for it, you can reply to this

[GitHub] log4net issue #16: (LOG4NET-467) .NET Core support

Github user bodewig commented on the issue: https://github.com/apache/log4net/pull/16 I think c661441 holds the necessary changes. Unfortunately assembling the release bits for log4net still requires two different VMs and about an hour of time, so I may need a few days before I can

[GitHub] log4net issue #16: (LOG4NET-467) .NET Core support

Github user bodewig commented on the issue: https://github.com/apache/log4net/pull/16 The [nuspec](https://github.com/apache/log4net/blob/trunk/log4net.nuspec) doesn't list any dependencies, this is because all dependencies of log4net are part of the framework for the Mono and .NET

[GitHub] log4net issue #16: (LOG4NET-467) .NET Core support

Github user SeanSnyders commented on the issue: https://github.com/apache/log4net/pull/16 @bodewig Yeah, I'm also trying to get my head around .Net Core project setup. Things have been quite a bit in flux! I think one will need to spec the dependencies, no? I could have it by

[GitHub] log4net issue #16: (LOG4NET-467) .NET Core support

Github user bodewig commented on the issue: https://github.com/apache/log4net/pull/16 Many thanks @SeanSnyders . You are the first one actually given the binaries a try - or the first one who tells us so. I've built the myget package using .NET Core 1.0.0 (SDK Preview 2), I

[GitHub] log4net issue #16: (LOG4NET-467) .NET Core support

Github user SeanSnyders commented on the issue: https://github.com/apache/log4net/pull/16 @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

[GitHub] log4net issue #16: (LOG4NET-467) .NET Core support

Github user derFunk commented on the issue: https://github.com/apache/log4net/pull/16 Awesome, thanks. I shared your cry for help on [Hacker News](https://news.ycombinator.com/item?id=12708507), maybe this gets some traction. Also you should maybe also add log4net here:

[GitHub] log4net issue #16: (LOG4NET-467) .NET Core support

Github user bodewig commented on the issue: https://github.com/apache/log4net/pull/16 OK, myget was simpler that I had expected. at least for a one-off publication:

[GitHub] log4net issue #16: (LOG4NET-467) .NET Core support

Github user bodewig commented on the issue: https://github.com/apache/log4net/pull/16 @derFunk the mailing list comment was meant to say that there may be things going on that one might miss when not following the list. I must admit there isn't that much going on:

[GitHub] log4net issue #16: (LOG4NET-467) .NET Core support

Github user derFunk commented on the issue: https://github.com/apache/log4net/pull/16 @bodewig sorry for not using the mailing list ;) one last thing: I'd love to test basically right now. I don't have a public NuGet repo at hands, would it be possible for you to push it somewhere?

[GitHub] log4net issue #16: (LOG4NET-467) .NET Core support

Github user bodewig commented on the issue: https://github.com/apache/log4net/pull/16 log4net development is coordinated via the mailing list :-) https://lists.apache.org/thread.html/3dafd7f063d6106ca9ca20379f5851a10e1588e9d1ce955d23e93a62@%3Clog4net-dev.logging.apache.org%3E

[GitHub] log4net issue #16: (LOG4NET-467) .NET Core support

Github user derFunk commented on the issue: https://github.com/apache/log4net/pull/16 AFAIU it seems we could have a NuGet package release already, or at least a pre-release. Is there anything else open we can help? Unfortunately only the NuGet repo owner can push. --- If

[GitHub] log4net issue #16: (LOG4NET-467) .NET Core support

Github user NachbarsLumpi commented on the issue: https://github.com/apache/log4net/pull/16 It is done when it is done. If you need it anytime sooner, get involved. On 3 Oct 2016 4:22 p.m., "Ibrar Mumtaz" wrote: > Hi, do you guys have a

[GitHub] log4net issue #16: (LOG4NET-467) .NET Core support

Github user iby-dev commented on the issue: https://github.com/apache/log4net/pull/16 Hi, do you guys have a release date for the new package? 2.0.6? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does

[GitHub] log4net issue #16: (LOG4NET-467) .NET Core support

Github user wjdavis5 commented on the issue: https://github.com/apache/log4net/pull/16 Oh I see, I misread that their chart there. Thanks for clarifying. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project

[GitHub] log4net issue #16: (LOG4NET-467) .NET Core support

Github user chlowell commented on the issue: https://github.com/apache/log4net/pull/16 Targeting `netstandard1.6` here is more limiting than useful. Doing so would remove support for current UWP apps, and the larger API surface won't light up any major features. --- If your project

[GitHub] log4net issue #16: (LOG4NET-467) .NET Core support

Github user wjdavis5 commented on the issue: https://github.com/apache/log4net/pull/16 Following the MSFT release yesterday - https://blogs.msdn.microsoft.com/dotnet/2016/09/26/introducing-net-standard/ It looks like this should be bumped to Net Standard 1.6 I did so

[GitHub] log4net issue #16: (LOG4NET-467) .NET Core support

Github user wjdavis5 commented on the issue: https://github.com/apache/log4net/pull/16 Hello, we are very patiently awaiting this next release. Thank you for putting this together. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub

[GitHub] log4net issue #16: (LOG4NET-467) .NET Core support

Github user bodewig commented on the issue: https://github.com/apache/log4net/pull/16 Thank you very much @chlowell @TAGC the code is in Apache's svn trunk and has been integrated with the build system by now. There are some lose ends and the biggest task is likely updating

[GitHub] log4net issue #16: (LOG4NET-467) .NET Core support

Github user TAGC commented on the issue: https://github.com/apache/log4net/pull/16 That's for the info. 👍 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes

[GitHub] log4net issue #16: (LOG4NET-467) .NET Core support

Github user TAGC commented on the issue: https://github.com/apache/log4net/pull/16 How far along is the .NET Core migration? I'm planning to migrate one of my projects that currently targets .NET Framework 4.5.2 to .NET Core and one of its dependencies is Log4Net. I only use

[GitHub] log4net issue #16: (LOG4NET-467) .NET Core support

Github user chlowell commented on the issue: https://github.com/apache/log4net/pull/16 No, there are significant differences. My first post details some important ones. .NET Framework 4.6 implements `netstandard1.3`. This means it exposes all the APIs specified by

[GitHub] log4net issue #16: (LOG4NET-467) .NET Core support

Github user chlowell commented on the issue: https://github.com/apache/log4net/pull/16 @bodewig I chose the version number to prevent any confusion between prerelease and published packages. There's no reason not to change it before release. I chose `netstandard1.3` because

[GitHub] log4net issue #16: (LOG4NET-467) .NET Core support

Github user bodewig commented on the issue: https://github.com/apache/log4net/pull/16 I'm not sure this applies here as we are still creating specific assemblies for .NET 2.0 up to 4.5 - and all of them are superior to the .NET Core DLL as they provide an ADO.NET appender, for

[GitHub] log4net issue #16: (LOG4NET-467) .NET Core support

Github user niemyjski commented on the issue: https://github.com/apache/log4net/pull/16 The lower the .net standard you can target the more places it will run. 1.0 can run every where (1.0, 1.6, etc). You should be targeting 1.3 here. --- If your project is set up for it, you can

[GitHub] log4net issue #16: (LOG4NET-467) .NET Core support

Github user bodewig commented on the issue: https://github.com/apache/log4net/pull/16 @chlowell maybe you can help us with two questions. Why did you chose netstandard1.3 as target and not, say, netstandard1.6. .NET Core 1.0 should provide the later AFAIU. Why did

[GitHub] log4net issue #16: (LOG4NET-467) .NET Core support

Github user bodewig commented on the issue: https://github.com/apache/log4net/pull/16 I've just diffed chlowell:log4net-core-pcl against my svn working copy of trunk and it looks as if there have been changes after the PR which makes identifying misses more difficult. I'll apply #30

[GitHub] log4net issue #16: (LOG4NET-467) .NET Core support

Github user bodewig commented on the issue: https://github.com/apache/log4net/pull/16 @jasonwilliams200OK, thanks, but too late, I went off fixing it myself before I saw you comment. :-) I'll diff my svn tree against a checkout of @chlowell's original branch to verify

[GitHub] log4net issue #16: (LOG4NET-467) .NET Core support

Github user jasonwilliams200OK commented on the issue: https://github.com/apache/log4net/pull/16 @bodewig, #30 fixed exactly this issue. Can you try with my branch? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your

[GitHub] log4net issue #16: (LOG4NET-467) .NET Core support

Github user bodewig commented on the issue: https://github.com/apache/log4net/pull/16 I've installed the Linux version, this is what happens for me: ``` Compiling log4net for .NETStandard,Version=v1.3 /usr/share/dotnet/dotnet compile-csc

[GitHub] log4net issue #16: (LOG4NET-467) .NET Core support

Github user jasonwilliams200OK commented on the issue: https://github.com/apache/log4net/pull/16 Fixed the build breakage and feedback in #30. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have

[GitHub] log4net issue #16: (LOG4NET-467) .NET Core support

Github user jasonwilliams200OK commented on the issue: https://github.com/apache/log4net/pull/16 Thanks a lot @bodewig! I am definitely willing to participate. I will test out the master and try to incorporate the feedback in subsequent PR pronto (before you start cutting the release

[GitHub] log4net issue #16: (LOG4NET-467) .NET Core support

Github user bodewig commented on the issue: https://github.com/apache/log4net/pull/16 Many thanks for your persistence. I have applied the patch as is as it didn't break anything of the existing build. But I haven't even tried to build the .NET Core part itself - I'll do so

[GitHub] log4net issue #16: (LOG4NET-467) .NET Core support

Github user chlowell commented on the issue: https://github.com/apache/log4net/pull/16 I updated this branch for .NET Core 1.0 rather than creating a new PR. The branch name is unfortunate--there's no longer a PCL involved--but I hope keeping this open is convenient for those