Support .NET Core 3.0, remove Travis integration

[304NotModified]

No description provided.

[304NotModified]

Dunno if recommend to target netcore 3

[304NotModified]

See also https://stackoverflow.com/questions/57846163/should-a-library-explicitly-target-net-core-3

[codecov-io]

Codecov Report

Merging #332 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #332   +/-   ##
=======================================
  Coverage   81.63%   81.63%           
=======================================
  Files          12       12           
  Lines        1127     1127           
  Branches      194      194           
=======================================
  Hits          920      920           
  Misses        140      140           
  Partials       67       67

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8d4d720...4d078e3. Read the comment docs.

[304NotModified]

@snakefoot
While I dislike building for an platform (netcore 3) and not netstandard, I think we should include this, otherwise an user could have dependency problems with .net core 3 (this one build Microsoft.Extensions.Logging v2 and using v3)

Do you agree?

[304NotModified]

(have to find how to fix Travis)

[snakefoot]

@304NotModified While I dislike building for an platform (netcore 3) and not netstandard, I think we should include this.

Think it is a good idea. Was considering netstandard2.1 but this is also supported by NetCore21, so it cannot be used as an option.

[snakefoot]

But please also update NLog.Extension.Hosting.

[snakefoot]

Guess the same operation is also needed on NLog.Web.AspNetCore 4.9

[304NotModified]

But please also update NLog.Extension.Hosting.

done, not tested yet locally (slow internet and VS needs an update)

[304NotModified]

Guess the same operation is also needed on NLog.Web.AspNetCore 4.9

I think also indeed

[304NotModified]

maybe needed: https://travis-ci.community/t/net-core-3-0-preview/1936/4

[jenscski]

@304NotModified While I dislike building for an platform (netcore 3) and not netstandard, I think we should include this.

Think it is a good idea. Was considering netstandard2.1 but this is also supported by NetCore21, so it cannot be used as an option.

NetCore21 does not support netstandard2.1, you need NetCore30 (https://github.com/dotnet/standard/blob/master/docs/versions/netstandard2.1.md), or am I lost here?

[snakefoot]

You are right. Netstandard 2.1 will not be supported by NetCore 2.1 and NetCore 2.2 Very certain that I read something else just a moment ago, but cannot find it. I think we should go for netstandard2.1 instead of netcore3 then Travis should also build "netstandard2.1" using NetCore3-preview

[304NotModified]

Yes, but the Ms extensions packages target explicit netcore3 and not netstandard2.1. Dunno why exactly

[snakefoot]

Yes, but the Ms extensions packages target explicit netcore3 and not netstandard2.1. Dunno why exactly

Yes that is a little weird. Maybe it is to better handle netcore3 and netcore31 for the same nuget-package. But didn't think netcore2 and netcore21 and netcore22 was a problem.

[304NotModified]

I gonna ignore Travis for a while.. maybe will remove the integration.

[304NotModified]

FYI API diff:

https://www.fuget.org/packages/Microsoft.Extensions.Logging/3.0.0/lib/netstandard2.0/diff/2.2.0/