When I try to build my vs2017 solution in Slick, it fails because MSBuild doesn't understand something in the csproj file.
The error:
error MSB4066: The attribute "Link" in element <Compile> is unrecognized.
error MSB4132: The tools version "15.0" is unrecognized.
Also, something creates "myProject.sln.cache" - I assume the old version of Msbuild does this?
Slick apparently adds some things to PATH:
C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE
C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\bin\amd64
C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\bin
C:\WINDOWS\Microsoft.NET\Framework64v4.0.30319
C:\Windows\Microsoft.NET\Framework64\v3.5
C:\Windows\Microsoft.NET\Framework64\v2.0.50727
C:\Program Files (x86)\Windows Kits\8.1\bin
But, this is a VS2017 project, so I would expect it to add VS2017 things to the path instead.
Turns out, I've got a lot of versions of MSBuild on my machine.
In this case, Slick ought to be using
C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\15.0\Bin\amd64\MSBuild.exe
When I specify the full path to that MSBuild in project->Properties->Build, I get another failure:
error MSB4126: The specified solution configuration "Debug|AnyCPU" is invalid.
Turns out, it needs to be "Any CPU" -- with a space.
In the attached solution, I've updated the path for MSBuild to demonstrate the "Any CPU" problem.
This is a freshly created solution direct from VS2017, then opened in Slickedit.