Use XAML-Builds with TFS 2018 Update 2

Question

We installed the newest TFS Server (TFS 2018 Update 2) which should run xaml builds. After the update, we started our agent, but our xaml-controller is still offline and I d

Answer 1

Thanks @PatrickLu-MSFT!! through your help, we found a workaround. Now we use one server for the Source Control etc. (TFS 2018) and another server only for the xaml-app-controller with TFS 2015. So we can build our projects, and have time to create new build definitions.

Answer 2

Yes, you can now upgrade to TFS 2018 Update 2 and continue to connect your XAML controllers and run XAML builds. When we removed support for XAML build in TFS 2018 RTW and Update 1, some of you could not upgrade due to having legacy XAML builds, and we want to unblock you. Although TFS 2018 Update 2 supports XAML builds for your legacy builds, XAML build is deprecated and there will be no further investment, so we highly recommend converting to a newer build definition format. See the Evolving TFS/Team Services build automation capabilities blog for more information about XAML build deprecation.

When you upgrade to TFS 2018 Update 2:

• If you have any XAML build data in your team project collection, you'll get a warning about the deprecation of XAML build features.
• You will need to use VS or Team Explorer 2017 to edit XAML build definitions or to queue new XAML builds.
• If you need to create new XAML build agents, you’ll need to install them using the TFS 2015 build agent installer.

XAML Build Controller/Agent info is now under Additional Tools and Components > XAML Build Configuration in the TFS Administration Console. Make sure your build services on the same server as your application tier. You possibly didn't re-configure your XAML build services after the upgrade. Try this and then check again.