-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NLog - NETSTANDARD1_5 #2341
NLog - NETSTANDARD1_5 #2341
Conversation
a2a1847
to
306d7d4
Compare
Codecov Report
@@ Coverage Diff @@
## master #2341 +/- ##
=======================================
+ Coverage 82% 82% +<1%
=======================================
Files 317 318 +1
Lines 22720 22771 +51
Branches 2782 2782
=======================================
+ Hits 18620 18666 +46
- Misses 3396 3402 +6
+ Partials 704 703 -1 |
looks good! (only checked the build result ;)) |
Think we should merge it after resolving the conflict? I'm doubting about the unit tests. (enabling for netstandard1.5) |
Allmost all tests are working after removing all those for features not available (ex. NLogTraceListener). Except the tests that checks current-class-logger for inner-classes where NetStandard1_5 uses "." as last delimiter (instead of "+") But it will require some effort to force the NetCoreApp2 to load the NetStandard1_5-dll. |
run it as NetCoreApp1? |
Well then I have to fix the UnitTest-project to work under NetStandard1_5 |
306d7d4
to
552532a
Compare
552532a
to
a50a765
Compare
@304NotModified after resolving the conflict? Conflicts resolved. |
should the unit tests run in .net standard 1.5, as you have changed the testbase? |
I have just made some changes, so it was easier to make local hack of adding NETSTANDARD1_5 to unit-test-project for NetCoreApp2 and removing NetStandard2.0 from Nlog.dll Not in any condition to perform the NetStandard1.5 testing in current state on the build-server. Would also have to fix the 10 tests that detects behavior change in StrackTrace-logic. |
OK thanks! Maybe later. I think we could run the tests on Travis in the future |
@304NotModified Guess you could create an issue about the missing testing of the NetStandard1.5 assembly (Like #1186 and #1184) |
Just checking if it can make a proper build