Use LogManager.LoadConfiguration + RC3

[snakefoot]

Resolves #242 (Updates to latest NLog.Extensions.Logging ver. 1.0.0-rc07 and also resolves #239)

[304NotModified]

thanks!

[codecov]

Codecov Report

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

@@          Coverage Diff          @@
##           master   #245   +/-   ##
=====================================
  Coverage      59%    59%           
=====================================
  Files          29     29           
  Lines         395    395           
  Branches       92     92           
=====================================
  Hits          233    233           
  Misses        126    126           
  Partials       36     36

---

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 b63748c...30b5d4e. Read the comment docs.

[snakefoot]

@304NotModified Can this also be merged?

[304NotModified]

yep, but have to check the version numbers here. It a bit out-dated

[snakefoot]

Nothing has happened in NLog.Web since the last dependency update.

[304NotModified]

I see it should be RC3 and that already in this PR :)

[304NotModified]

thanks!

[snakefoot]

@304NotModified Found a bug, when doing AspNetCore1.1 Apps. Then it will fail to automatically register the NLog.Web.AspNetCore-assembly.

Looks like the AspNetCoreTests are not run for NetCoreApp1.1. Will try and fix that, so this bug would have been caught.

[snakefoot]

@304NotModified After further investigation, then this was intended behavior (had to manual register assembly):

https://github.com/NLog/NLog.Web/wiki/Getting-started-with-ASP.NET-Core-(csproj---vs2017)

I have now created #249 to improve this.