Today we released updates to FinalBuilder (184.108.40.2067) and Continua CI (220.127.116.11) which add support for Visual Studio 2017 RC.
There were a few issues we found with Visual Studio 2017 Release Candidate. The first was, unlike every other previous version of Visual Studio, 2017 RC does not write any useful information to the registry that allows us to reliably find out where it was installed to. So at the moment, we just check the default install locations :
On 64 bit windows :
C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE
C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE
C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE
on 32 bit windows (do people still use it?) :
C:\Program Files\Microsoft Visual Studio\2017\Community\Common7\IDE\Common7\IDE
C:\Program Files\Microsoft Visual Studio\2017\Professional\Common7\IDE
C:\Program Files\Microsoft Visual Studio\2017\Enterprise\Common7\IDE
Yes, each edition now installs into different folders.
As a work around for those who don't install in the default location, you can set environment variables MSBuild15Path (for MSBuild) and VisualStudio2017Path for Visual Studio, if we don't find VS/MSBuild in the default locations, we'll check for those environment variables.
Another issue we found is that when building with devenv.com (ie the visual studio command line, rather than msbuild), builds take a looooong time.. it appears to hang after building, and it also seems to randomly fail with windows error 80131623 (FatalExecutionEngineError). This has nothing to do with FinalBuilder or Continua CI, it happens on the command line as well. I have reported these issues to microsoft, hopefully they will resolve them before release. On the MSBuild Action in FinalBuilder, we were not able to get the list of targets for a dotnet core project. This is still being investigated, we do still hope to resolve this eventually.
Note, since this work was done against a Release Candidate, things may change between now and the VS2017 RTM release (microsoft seem to have redifined what a release candidate is lately!). If you find any issues let us know.
BTW, TFS 2017 support is currently being worked on for both FinalBuilder and Continua CI. We should have a VSO FinalBuilder build task available in the marketplace soon (it's close). However, getting our xaml builds working with TFS2017 is proving challenging (just like previous releases), there is no doco and it's deprecated (good riddance) and visual studio won't load our projects.. stay tuned.