Hi Borja,
Please join and reply to the mailing list so that this conversation is
both archived and available to the general public.
The system.runtime.interopservices assembly with version 4.3.0 should
work when targeted against netstandard-1.3. My information comes from
the site https://www.nuget.org/packages/system.runtime.interopservices/.
With this change, I observed that the errors / warnings go away and a
netcoreapp2.0 that uses log4net and the mentioned transient dependency
should work without any other changes or side effects. For now this is
just theory despite being used by the log4net tests. These changes are
available in the mentioned feature branch. Since you noticed this issue
too, it would be awesome if you or others evaluated whether these
changes are fine and work in your/their environment. I have very limited
knowledge about how people use log4net in a netstandard application and
any help or insights are therefore greatly appreciated.
Best regards,
Dominik
On 2017-12-12 10:03, Borja Ruiz Arroyo wrote:
Hello,
I'm not sure what do you want to ask.
Previously the NU1605 was a warning, but now by default, it's an error.
These warnings/errors occur because the references of the netcoreapp2.0 are a
newer version than the version included as dependencies in the log4net package.
As you only want to support the netstandard-1.3, maybe you cannot upgrade them
(I'm not sure about the version referenced by the netstandard-1.3). But in the
meantime, the application using the netcoreapp2.0 (netstandard-2.0), will
through this error.
Best regards,
Borja
From: Dominik Psenner [mailto:[email protected]]
Sent: lunes, 11 de diciembre de 2017 22:58
To: Borja Ruiz Arroyo
Cc: Logging PMC; [email protected]<mailto:[email protected]>
Subject: Re: [NuGet Gallery] Message for owners of the package 'log4net'
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]<mailto:[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
