-
Notifications
You must be signed in to change notification settings - Fork 977
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
[WIP] netstandard support #171
Conversation
Thank you for your contribution. -Neil |
@ViktorHofer I just grabbed latest and ran it in VS2017 - correct that .Tests doesn't compile and .netcore2.0 fails the restore for Bootstrapper? |
@christophwille Tests do compile. Just quite different as before with a console wrapper around it as nunit does not support netcoreapp yet. As mentioned 3 tests are failing right now. I had no restore errors... @McNeight Thanks for the fine words, but I didn't expect you to merge it instantly as I marked it with WIP - Work in Progress. I did most of the work for porting it to netstandard but there are still some rough parts that need to be fixed --> see the issue. |
Ok, then something is different in my setup because it doesn't (clean checkout, rtm vs2017): Restoring NuGet packages... |
Also, doesn't this break support for older VS versions? |
Yes, definitely breaks compatibility with older versions as .NET Standard and .NET Core tooling isn't available (despite a pre-release version) before VS 2017. |
http://www.alteridem.net/2017/05/04/test-net-core-nunit-vs2017/ would that help us in any way to make it work better? |
@ViktorHofer I used VS2017 U3 to update to preview2. Builds & runs now. Do you happen to know if there now would be a better Core-way of running NUnit tests? |
@ViktorHofer also in the vein of Unit Test questions: the currently failing three ones - did those come from the replatforming / changes? Because I don't see those failures on @McNeight older builds. |
@christophwille again as I mentioned several times already, I intended to help porting the library to netstandard but nothing besides that. I was surprised when I saw my PR already merged as I mentioned issues of my port. I currently can't spend any time on this project. You might try to resolve the test failures on your own...
This is a better question for the nunit team. I did a quick research and it seems there is an alpha version of nunit for VS2017 with the sdk project format out now: https://github.com/nunit/nunit3-vs-adapter/releases/tag/3.8-alpha1 |
@ViktorHofer NUnit now running smoothly, test failures resolved (not really netstandard-related as it turned out). |
Perfect, glad to here that :) |
I certify that I own, and have sufficient rights to contribute, all source code and related material intended to be compiled or integrated with the source code for the SharpZipLib open source product (the "Contribution"). My Contribution is licensed under the MIT License.
.NET Standard support. Currently 3 tests are failing with netcore2.0.
appveyor also needs to be adjusted. some links maybe too? please contribute!
#106 (comment)