-
Notifications
You must be signed in to change notification settings - Fork 748
Convert Portable library to .NET Standard 1.3 #2092
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
Comments
I should also state that I don't want to drop the 1.6 version as it adds back in functionality that is not available in the portable library or .NET Standard 1.3. I see them as complimenting each other. |
Seems like a good way to go. |
Sounds good to me. |
I like it. According to @codito, |
@jnm2 I was hoping to target 1.0 if possible, 1.3 if not. |
@rprouse That sounds good. Since all the APIs in the portable project's current target are also in |
@rprouse What is the latest NUnit version supporting .NET Standard 1.0 ? |
@NN--- We supported Profile259 which is equivalent to .NET Standard 1.0 (https://docs.microsoft.com/en-us/dotnet/standard/net-standard#pcl-compatibility) up to and including https://www.nuget.org/packages/NUnit/3.6.1 and then switched to .NET Standard 1.3 in 3.7. The only use for .NET Standard 1.0-1.3 is if you target the discontinued Windows 8/Windows Phone 8/Windows Phone Silverlight frameworks: |
I tried to install 3.6.1 on .NET Standard 1.2 and it didn't work for me. |
@NN--- Where was the failure and what was the message? |
|
This is the problem: dotnet/sdk#391 We got it installed with the workaround described there |
The portable library is .NET Standard 1.3 (or possibly 1.0 or 1.1), but it cannot easily be installed in a .NET Standard 1.3 project. Attempting to do so results in the following error,
If we convert the project to the lowest .NET Standard version it supports instead of PCL, it will still work in all the PCL targets, plus it will work in .NET Standard.
Before we do this, can anyone see any issues with this approach?
The text was updated successfully, but these errors were encountered: