Solution does not build from 2017

[goofballLogic]

The project does not build from VS2017 (appears to be hard-wired to 2015).
Attempting the upgrade process leaves errors:

Severity Code Description Project File Line Suppression State
Error The TargetFramework value 'net40-client' was not recognized. It may be misspelled. If not, then the TargetFrameworkIdentifier and/or TargetFrameworkVersion properties must be specified explicitly. json-ld.net C:\Program Files\dotnet\sdk\2.0.3\Sdks\Microsoft.NET.Sdk\build\Microsoft.NET.TargetFrameworkInference.targets 96
Error MSB3202 The project file "C:\src\json-ld.net\test\json-ld.net.tests\json-ld.net.tests.xproj" was not found. json-ld.net.tests C:\Users\andrew.gibson\AppData\Local\Temp\tmpa2e93ef2820d47cfbc8cf44fb5e8602f.proj 28
Error MSB4226 The imported project "C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\Microsoft\VisualStudio\v15.0\DotNet\Microsoft.DotNet.Props" was not found. Also, tried to find "DotNet\Microsoft.DotNet.Props" in the fallback search path(s) for $(VSToolsPath) - "C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v15.0" . These search paths are defined in "C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\15.0\Bin\MSBuild.exe.Config". Confirm that the path in the declaration is correct, and that the file exists on disk in one of the search paths. json-ld.net C:\src\json-ld.net\src\json-ld.net\json-ld.net.xproj 8

Are you open to this solution being ported to 2017?

[goofballLogic]

Moving the broken tests part of this issue into a new one (for a pull request)

[xivk]

I think this will be fixed with the pull-request here:

#37

Would it be OK to remove the net40-client and portable profiles as they have become obsolete? The old package will still be there for those still on those platforms.

[goofballLogic]

Sounds good

…

On 27 Sep 2018, 07:36, at 07:36, Ben Abelshausen ***@***.***> wrote: I think this will be fixed with the pull-request here: #37 Would it be OK to remove the `net40-client` and portable profiles as they have become obsolete? The old package will still be there for those still on those platforms. -- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: #22 (comment)

[stale]

This issue has been automatically marked as stale because it has not had recent activity. After 30 days from now, it will be closed if no further activity occurs. Thank you for your contributions.