[jira] [Commented] (LOG4NET-467) Is .NET Core, will be supported in the near future, or not

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on LOG4NET-467:


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.


> 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: 1.2.16
>
> 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
(v6.3.4#6332)

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

[niemyjski]

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 reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

[bodewig]

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 you chose the version 3.0.0? To me it looks as if 2.1 would be fine 
if we wanted to unify the versions of the nuget package and the assemblies.


---
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 so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: NAnt and Mono (was Re: Happy to help)

[Ryan Boggs]

On Sep 12, 2016 7:43 AM, "Stefan Bodewig"  wrote:
>
> On 2016-09-12, Ryan Boggs wrote:
>
> > On Sep 12, 2016 1:43 AM, "Stefan Bodewig"  wrote:
>
> >> It looks as if System.dll now resides in mono/4.0-api rather than
> >> mono/4.0 (the later only holds Mono.Posix.dll and mscorlib.dll).
>
> > Ok, initial glance tells me that this could be fixed simply by updating
the
> > app.config file to look in the new *-api directories. I can try to fix
this
> > if time allows.
>
> Thanks.
>
> > Are you trying to build the log4net from the master branch?
>
> trunk - log4net is still in svn. :-)
Ah, ok.
>
> > And what platform are you using to build?Linux?
>
> The error occured on Linux which is where I do all my development.
>
> My preference would be able to use Mono on Windows as well so that I can
> build a log4net release for all supported platforms in a single build
> process. Unfortunately NAnt doesn't seem to detect any version of Mono
> I've installed on my Win7 VM at all. I tried Mono 3.12.1 and 4.4.2.11.

Yeah, i noticed that this morning as well. Looks like i never got around to
putting in that setup after they fixed the registry settings in the
installer.  Since (i think off the top of my head) this is also in the
app.config file, i can try to kill two birds with one stone. Ill see what i
can do.

Thanks,
Ryan
>
> Stefan

Re: NAnt and Mono (was Re: Happy to help)

[Stefan Bodewig]

On 2016-09-12, Ryan Boggs wrote:

> On Sep 12, 2016 1:43 AM, "Stefan Bodewig"  wrote:

>> It looks as if System.dll now resides in mono/4.0-api rather than
>> mono/4.0 (the later only holds Mono.Posix.dll and mscorlib.dll).

> Ok, initial glance tells me that this could be fixed simply by updating the
> app.config file to look in the new *-api directories. I can try to fix this
> if time allows.

Thanks.

> Are you trying to build the log4net from the master branch?

trunk - log4net is still in svn. :-)

> And what platform are you using to build?Linux?

The error occured on Linux which is where I do all my development.

My preference would be able to use Mono on Windows as well so that I can
build a log4net release for all supported platforms in a single build
process. Unfortunately NAnt doesn't seem to detect any version of Mono
I've installed on my Win7 VM at all. I tried Mono 3.12.1 and 4.4.2.11.

Stefan

Re: NAnt and Mono (was Re: Happy to help)

[Ryan Boggs]

On Sep 12, 2016 1:43 AM, "Stefan Bodewig"  wrote:
>
> On 2016-09-11, Ryan Boggs wrote:
>
> > On Sep 11, 2016 9:21 AM, "Stefan Bodewig"  wrote:
>
> >> On 2016-09-11, Ryan Boggs wrote:
>
> >>> On Sep 11, 2016 2:23 AM, "Stefan Bodewig"  wrote:
>
>  On 2016-09-09, Ryan Boggs wrote:
>
> > Fyi - One thing i do know regarding NAnt, mono, and windows is that
> > when
> > they updated the installer for 4, they omitted the registry settings
> > for
> > the first couple of releases so NAnt couldn't find it.
>
>  I went back to 3.12.1 after your comment but NAnt 0.92 still doesn't
>  recognize Mono.
>
>  On Linux things aren't really any better as NAnt considers Mono 4.x
as
>  "mono-4.5" framework and won't build anything at all as the framework
> > is
>  not supported. And it really doesn't seem to find the compiler and
>  reference assemblies (that are likely not there, anyway) when I run
> > Nant
>  with -t:mono-4.0
>
> >>> What version of NAnt are you using?
>
> >> 0.92 downloaded from the project site.
> > Can you do me a favor and try it with the last nightly build? I did
commit
> > some changes related to mono-4.5 that should be in that build.
>
> At least it doesn't complain about mono-4.5 not being supported but when
> trying to build log4net
>
> ,
> | $ nant
> | WARNING: The runtime version supported by this application is
unavailable.
> | Using default runtime: v4.0.30319
> | NAnt 0.93 (Build 0.93.5521.0; nightly; 12.02.2015)
> | Copyright (C) 2001-2015 Gerry Shaw
> | http://nant.sourceforge.net
> |
> |
> | BUILD FAILED
> |
> | Mono 4.0 Profile (mono-4.0) is not installed, or not correctly
configured.
> |
> | The 'System.dll' assembly does not exist in framework assembly
directory '/usr/lib/pkgconfig/../../lib/mono/4.0'.
> |
> | For more information regarding the cause of the build failure, run the
build again in debug mode.
> |
> | Try 'nant -help' for more information
> `
>
> It looks as if System.dll now resides in mono/4.0-api rather than
> mono/4.0 (the later only holds Mono.Posix.dll and mscorlib.dll).

Ok, initial glance tells me that this could be fixed simply by updating the
app.config file to look in the new *-api directories. I can try to fix this
if time allows. Are you trying to build the log4net from the master branch?
And what platform are you using to build?Linux?

Thanks,
Ryan
>
> Stefan

Re: NAnt and Mono (was Re: Happy to help)

[Stefan Bodewig]

On 2016-09-11, Ryan Boggs wrote:

> On Sep 11, 2016 9:21 AM, "Stefan Bodewig"  wrote:

>> On 2016-09-11, Ryan Boggs wrote:

>>> On Sep 11, 2016 2:23 AM, "Stefan Bodewig"  wrote:

 On 2016-09-09, Ryan Boggs wrote:

> Fyi - One thing i do know regarding NAnt, mono, and windows is that
> when
> they updated the installer for 4, they omitted the registry settings
> for
> the first couple of releases so NAnt couldn't find it.

 I went back to 3.12.1 after your comment but NAnt 0.92 still doesn't
 recognize Mono.

 On Linux things aren't really any better as NAnt considers Mono 4.x as
 "mono-4.5" framework and won't build anything at all as the framework
> is
 not supported. And it really doesn't seem to find the compiler and
 reference assemblies (that are likely not there, anyway) when I run
> Nant
 with -t:mono-4.0

>>> What version of NAnt are you using?

>> 0.92 downloaded from the project site.
> Can you do me a favor and try it with the last nightly build? I did commit
> some changes related to mono-4.5 that should be in that build.

At least it doesn't complain about mono-4.5 not being supported but when
trying to build log4net

,
| $ nant
| WARNING: The runtime version supported by this application is unavailable.
| Using default runtime: v4.0.30319
| NAnt 0.93 (Build 0.93.5521.0; nightly; 12.02.2015)
| Copyright (C) 2001-2015 Gerry Shaw
| http://nant.sourceforge.net
| 
| 
| BUILD FAILED
| 
| Mono 4.0 Profile (mono-4.0) is not installed, or not correctly configured.
| 
| The 'System.dll' assembly does not exist in framework assembly directory 
'/usr/lib/pkgconfig/../../lib/mono/4.0'.
| 
| For more information regarding the cause of the build failure, run the build 
again in debug mode.
| 
| Try 'nant -help' for more information
`

It looks as if System.dll now resides in mono/4.0-api rather than
mono/4.0 (the later only holds Mono.Posix.dll and mscorlib.dll).

Stefan