I'd be willing to lend a hand. Some ideas:
* Just be bold and embrace .NET 4.5, CoreCLR and the current version of
Mono (must build on Centos7 with the official mono yum repo). Anyone with
an XP requirement will either stick to the old log4net for now, or we've
already lost them to NLog or whatever. Let's make a great modern piece of
software, and not worry about abandoning legacy users that have plenty of
options.
* Why .NET 4.5? async/await mainly.
* Forget supporting the current appenders. Its not hard to write an
{obscure RDBMS appender} from scratch, and someone from that community is
always willing to do that.
* Console and text file should be all that we need to ship, but anything
that will run on a stock windows OS (or with official MSFT updates like
newer SQL drivers) should be considered for 1.0 release if someone will
write them.
* What we do need with the appender interface is install/uninstall hooks.
There should be a pipeline for appending install and uninstall Func<>()s so
the users can hook into them. This way a program can have an "install
appender target" or "uninstall appender target" mode. This is important for
databases (creating the table), or an eventlog appender where you need to
install an event source as admin but your program runs unprivileged.
Justin
On Wed, Aug 19, 2015 at 7:48 AM Ílson Bolzan <ilbol...@gmail.com> wrote:
> Agree.
>
> Will the code be compatible with the current version?
>
> On Wed, Aug 19, 2015 at 8:03 AM, Miroslav Vanický <
> miroslav.vani...@vande.cz> wrote:
>
>> Logging to MSSQL would be nice!
>>
>>
>> On 19.8.2015 12:56, Javier Sanchez wrote:
>>
>> Agree!
>> El ago. 19, 2015 3:21 AM, <dpsen...@apache.org> escribió:
>>
>>> Hi,
>>>
>>>
>>>
>>> Last night I’ve dreamed a dream and in that dream the release process of
>>> log4net happened on a flick of a switch. Now that I’m awake again I find
>>> the idea most pleasing and thus I’m bringing this idea to the dev list [1].
>>>
>>>
>>>
>>> My idea was that we should start off log4net2 “from scratch” that
>>> targets only .NET 4.0 [2] and does only what the largest part of people
>>> want from it:
>>>
>>>
>>>
>>> 1. Log to console
>>>
>>> 2. Log to file [3]
>>>
>>>
>>>
>>> What can also be discussed is if log4net2 should get an interface to the
>>> existing appenders.
>>>
>>>
>>>
>>> Please discuss!
>>>
>>>
>>>
>>> Cheers,
>>>
>>> Dominik
>>>
>>>
>>>
>>> [1] To make this come true there will be the need for a few helping
>>> hands and therefore this message goes to people that use log4net and want
>>> log4net to be revived.
>>>
>>> [2] With .NET 4.0 we would still support good old WinXP and that should
>>> really be enough for today’s technology.
>>>
>>> [3] Yes, with rolling and there shouldn’t be a thousand possible
>>> combinations of configuration options. Stability and speed goes over
>>> functionality.
>>>
>>>
>>>
>>
>>
>
>
> --
>
>
