Hi Borja, please ask future questions on one of the official mailing lists, as documented here:
https://logging.apache.org/log4net/mail-lists.html As for your question, there is ongoing work to support netstandard-2.0 as a target along with automating the build process. While implementing these two we noticed that the initial support for the netstandard-1.3 target was half baked and we are in the process of implementing proper building and testing of the netstandard-1.3 target. The plan is to add netstandard-2.0 as a target only after that. While looking at the netstandard-1.3 stuff I noticed your observation about the package downgrades too. I fixed that by upgrading the downgraded packages. If my memory does not betray me, it should be the feature branch named "feature/cd-pipeline". As noted earlier, this is a work in progress and not finished yet. We would be happy if you or your company decided to help us, it would certainly let things move faster. Do you think upgrading the packages is actually a good idea? Do you happen to know how this could happen in the first place? Best regards 2017-12-11 19:13 GMT+01:00 NuGet Gallery <[email protected]>: > *User bruiz <obfuscated> sends the following message to the owners of > Package 'log4net'.* > > Hello, > > After installing the log4net 2.0.8 package, the compiler shows an error > when I try to publish my app. > > You do as follows: dotnet new console dotnet add-package log4net --version > 2.0.8 dotnet publish -r win10-x64 > > And then you get: error NU1605: Detected package downgrade: > System.Runtime.InteropServices from 4.3.0 to 4.1.0. > > You can fix it adding the following to your csproj under PropertyGroup > <NoWarn>$(NoWarn);NU1605</NoWarn> > > The problem is the log4net package references that are not upgraded for > netcoreapp 2.0. Please, would you mind to upgrade them? > > Thanks in advance. Best regards, > > Borja > > > -- Dominik Psenner
