Just wondering what will be required to use FinalBuilder with TFS 2017.
I assume we will require a new XAML build definition, and also potentially a new version of FinalBuilder for TFS related actions?
Is there any predicted release date to accommodate these changes?
I can’t provide any accurate eta on support for TFS2017, at the moment we’re working on VS 2017 support, once that’s done we’ll look at TFS 2017. In our experience adding support for new TFS versions typically take a few weeks to sort out, but really it just depends on how much has changed.
Not even sure yet if xaml builds are still supported, but we do have a vso task for tfs2015 (again, will have to see what needs changing).
Hi Chris
We are still looking into xaml build support in TFS2017. So far we have not managed to build our code activities, VS2017 RC seems to be missing the msbuild task to build xaml so we are stuck on that for now (this is the issue : https://developercommunity.visualstudio.com/content/problem/2476/cannot-build-project-that-contains-windows-workflo.html )
It looks like the xaml template format has changed a lot, not sure why they would change it so much when they deprecated it, and try hard to avoid having customers use it (it’s not enabled out of the box, you have to go and configure the server with xaml build controller).
On the positive side, we now have our FinalBuilder VSO task available via the Visual Studio Market Place, so it can be installed into TFS (online or on premise) from within the web interface (install button for online, download for on premise). This task works with TFS2015 and TFS2017.
It doesn’t appear as though microsoft have any sort of conversion from xaml to vnext build definitions, so conversion is a start again sort of thing. Using the FinalBuilder VSO task is pretty easy, and it really does work very well (don’t forget to install FinalBuilder on the agents).