g to consider for log4net.
Regards,
Gert
PS. Sorry for the reply format (Outlook ...).
-Original Message-
From: Stefan Bodewig [mailto:bode...@apache.org]
Sent: zondag 11 september 2016 12:25
To: 'Log4NET Dev'
Subject: Re: netstandard version of the .NET Core build
On 2016-09-1
HI Stefan,
I suppose it's 1.3 because 1.0 has an even more limited API surface.
A lot of CoreFX packages are not available for netstandard 1.0.
For SSH.NET - an OSS project I spend most of my time on right now - I also
chose 1.3 because of this.
Regards,
Gert
-Original Message-
From: Ste
Hey Stefan,
I've got my hands full at the moment, but I'll try to step up and contribute
to log4net on a best effort basis.
Surely don't want to let log4net fade out.
Regards,
Gert
-Original Message-
From: Stefan Bodewig [mailto:bode...@apache.org]
Sent: dinsdag 6 september 2016 06:12
T
Sorry about that.
I've been slow scanning through my emails.
-Oorspronkelijk bericht-
Van: "Dominik Psenner"
Verzonden: 6/02/2014 8:07
Aan: "'Log4NET Dev'"
Onderwerp: AW: Thoughts on 1.3
That's exactly what I had pointed out in the original thread. :-)
>-Ursprüngliche Nachricht-
Hey Miljenko,
I don't think it makes sense to create a separate "client-profile" version.
MS has already abandoned this:
http://msdn.microsoft.com/en-us/library/cc656912(v=vs.110).aspx
Perhaps you were referring to a portable class library ?
Cheers,
Gert
- Oorspronkelijk bericht -
Van:
Hi Stefan,
If I recall correctly, the CF tools are/were only available as part of Visual
Studio.
I can provide you with the .NET Framework 1.0 redistributable, SDK and SP3 if
you still need them.
Regards,
Gert
- Original Message -
From: "Stefan Bodewig"
To: log4net-dev@logging.apache.
Hey,
Anyone happen to know if an upgrade of Mono or NAnt was done prior to this
failure?
Gert
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: maandag 10 maart 2008 10:03
To: log4net-dev@logging.apache.org
Subject: [EMAIL PROTECTED]: Project logging-log4net (in
[
https://issues.apache.org/jira/browse/LOG4NET-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12474368
]
Gert Driesen commented on LOG4NET-114:
--
For now, I guess we should only run the tests again the current
+1
> -Original Message-
> From: Curt Arnold [mailto:[EMAIL PROTECTED]
> Sent: woensdag 14 februari 2007 18:44
> To: Log4NET Dev
> Subject: Re: [VOTE][RESULT] Graduating the incubator
>
> Sorry about that. Nicko Cadell (PMC) +1
>
> I have called for a vote on [EMAIL PROTECTED] Anyone wh
+1, but with a few (silly) questions/remarks:
- in the .NETCF version, there are two separate references to coredll.dll:
one named coredll.dll and one named CoreDll.dll. Not that this really does
any harm, but ...
- was it intentional to also include the xdocs directory in the distribution
packag
> -Original Message-
> From: Nicko Cadell [mailto:[EMAIL PROTECTED]
> Sent: donderdag 15 december 2005 17:39
> To: Log4NET Dev
> Subject: Building Mono from source
>
> Gert,
>
> Are you building Mono from source on Windows? I was trying to
> follow the
> very simple instructions on h
Nicko,
All Mono-related issue have been fixed in Mono svn. I reported a bunch of
issues during the process of getting log4net building on Mono again (without
warning), and all of them are definitely fixed (by Atsushi).
There might still be one issue that not been merged into gmcs, but log4net
com
[
http://issues.apache.org/jira/browse/LOG4NET-58?page=comments#action_12357669 ]
Gert Driesen commented on LOG4NET-58:
-
Recent nightly builds of NAnt (http://nant.sourceforge.net/nightly/latest) do
support .NET 2.0 RTM.
I'll also be worki
> -Original Message-
> From: Nicko Cadell [mailto:[EMAIL PROTECTED]
> Sent: zondag 20 februari 2005 19:50
> To: Log4NET Dev
> Subject: [POLL] Issue Tracking
>
> Hi all,
>
> Log4net does not currently maintain an issue tracking system. The old
> sourceforge tracker is no longer being m
Definitely +1 on this !
> -Original Message-
> From: Nicko Cadell [mailto:[EMAIL PROTECTED]
> Sent: zondag 20 februari 2005 19:43
> To: Log4NET Dev
> Subject: [POLL] New Release 1.2.9 Beta
>
> Hi all,
>
> It has been rather a long time since the last beta release of log4net,
> and an
ocuments\Dev\dotNET\Frameworks\logging-log4net\log4net.build(409,14):
> External Program Failed: D:\Program Files\Mono-1.0.2\lib\mono/1.0/mcs.exe
(return code was 1)
>
> Total time: 4.9 seconds.
>
>
> C:\Documents and Settings\jonathan\My
Documents\Dev\dotNET\Frameworks\logging-log
Jonathan,
The reason why the Mono 1.0 installation is not detected, is because the key
where Mono registers itself in the registry changed after the 1.0 release
(from HKLM\Software\Mono to HKLM\Software\Novell\Mono), and recent nightly
builds of NAnt now only check in the new location
(HKLM\Softwa
- Original Message -
From: "Nicko Cadell" <[EMAIL PROTECTED]>
To: "'Log4NET Dev'"
Sent: Sunday, May 23, 2004 5:51 PM
Subject: RE: Building under Mono 1.0 beta
> Gert,
>
> Using the updated build 0.91.99 gives me the same error.
> I have attached the output of the nant build to this ema
Nicko,
I have no problem building a CLS compliant log4net with mono built from cvs
(on windows).
Can you try a more recent installer for Windows :
http://primates.ximian.com/~gonzalo/mono/blog/files/mono-0.91.99-win32-3.exe
You will need to update your NAnt configuration file though (I attached
19 matches
Mail list logo
