Similar to this question, except we are not using gated check-in. We were on TFS 2013 Update 4, and recently upgraded to 2017 Update 1. Our XAML builds will run once successfully after a service restart, and then fail with permission denied errors. When I check the server, it is because the NUnit files are locked by the build service.
Has anyone been able to get past this without moving to vNext?
The TfsBuildServiceHost.exe holds a handle to the NUnit test adapter assemblies. And then will get an Exception Message: Access to the path '<assemblyfilepath>' is denied. Seems to be a bug.Take a look at this similar issue:TFSBuildServiceHost maintains a lock on assemblies, TFS 2015 You could submit a Bug in this new place Develop Community-Team Foundation Server and will get quick response by develop team.
Moreover, XAML Build are deprecated in TFS 2017 and will not be available in tge next version of TFS. VSTS already no longer supports them.
I'm looking for the hosted XAML build controller. Where did it go?
The hosted XAML build controller is no longer supported. Accounts created on or after April 2016 do not have access to it. We plan to remove the hosted XAML build controller from all accounts, possibly as soon as March 2017.
Highly recommend you to convert your builds to vNext Build to access some new technology and support. For more please refer Why Should I Leave XAML Builds?