Targeting .NET Standard 1.0 will allow the library the greatest compatibility across framework versions. The test project is converted to be a .NET Core 1.0 Console App.
There may be further changes needed. For example, in building the NuGet package, it would best to use dotnet pack rather than invoke NuGet directly.
I saw your comment on #53 about submitting a differently named project file/solution file. I have done an in-place upgrade, admittedly, but:
.NET Core SDK 1.0 is only supported in VS 2017
IMHO it is plenty feasible (especially with a project this simple) to use VSCode or another lightweight editor.
alastairs
commented
7 years ago
Targeting .NET Standard 1.0 will allow the library the greatest compatibility across framework versions. The test project is converted to be a .NET Core 1.0 Console App.
There may be further changes needed. For example, in building the NuGet package, it would best to use
dotnet packrather than invoke NuGet directly.I saw your comment on #53 about submitting a differently named project file/solution file. I have done an in-place upgrade, admittedly, but: