-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Does Azure Devops server still support XAML builds? #22
Comments
Hi @sunzhaolin , adding @aaronhallberg to help out here! :) |
I'd like to know this too. We just updated, but are thinking of rolling backwards because all of the XAML agents are offline and the logfiles say to update. I'm guess, no, 2019 does not support XAML builds. Great...... |
Any official answer for this? |
@aaronhallberg Can someone take a look at this? We aren't ready to upgrade our XAML build definitions yet, but we want to upgrade our on-prem TFS 2015 to Azure DevOps 2019. What is the proper way to do this and still have XAML builds working? |
@vijayma should say for sure, but I am reasonably confident that XAML Build is still as supported in Azure DevOps Server 2019/2020 as it was in TFS 2018 Update 2. That is, you can continue to use it, but we are not investing in new features, encourage you to migrate to our newer system, etc. |
When we installed TFS 2019, the "XAML Build Configuration" node wasn't visible in the TFS Admin Console, like it was with TFS 2015. Is there something we're missing? |
Ya, you have to use an older version of the management console to configure controllers and agents. See https://developercommunity.visualstudio.com/content/problem/256956/after-upgrading-to-tfs-2018-update-2-the-xaml-buil.html, for a bit more info. |
@aaronhallberg Do you happen to know how to access the old management console? I tried copying it from the old server, but that didn't work. |
we have TFS 2018 update 2 right now and still using some XAML builds for our deployment. wonder if those XAML builds can still use on the new Azure Devops server 2019?
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
The text was updated successfully, but these errors were encountered: