Closed alexbarbato closed 7 years ago
Should we also consider updating the .NET Standard framework from 1.5?
Backlogging this for now as the benefits of updating to 2.0 don't seem to outweigh the backwards compatability costs. Correlated to 17417 (internal)
Eventually we may reopen this issue and integrate the change. The reasoning for now is that we want to cast as wide a net as we can so many people can use this library. By updating to .net core 2.0, we restrict ourselves to only projects that are also 2.0. Whereas being on .net core 1.1, any 1.1 or 2.0 project can utilize it.
There are definitely benefits to 2.0, so we will want to revisit. Possibly we need to create a separate package for 2.0 support? This may depend on how best to handle it in nuget.
Possible Solution
Update dotnet sdk to 2.0
Detailed Description
We are currently running on 1.1 and could probably do to update to the most current implementation