CODEWITHSUNDEEP
xamlvisual-studio-2015tfs-2015tfs-process-templatebuild-process-template
Brian Chambers
Brian Chambers

Reputation: 523

Using Saved Unchanged XAML Build Process File Causes Build To Fail

I am getting the following build error when using my "custom" XAML process build file:

(-1, 0)
TF215097: An error occurred while initializing a build for build definition >\Test2\TestProject1: Exception Message: Cannot set unknown member 'Microsoft.TeamFoundation.Build.Activities.RunScript.FailOnNonZeroExitCode'. (type XamlObjectWriterException)

Steps to Reproduce

  1. Download the TfvcTemplate.12.xaml file to local storage
  2. Open the template in the XAML visual editor (in new project or standalone)
  3. Save the template (NOTE: this adds lots of extra XAML markup for some reason)
  4. Commit the template to TFS
  5. Import the template into the Process section of my build definition
  6. Refresh the build process file
  7. Queue a build using the "new" template

I haven't seen anything on StackOverflow or the ASP.NET forums regarding this particular error message in regards to saving the exact same file and using it again. I have resorted to editing the XAML manually so that the extra markup doesn't break my build, but I'd much rather use the Toolbox to configure my workflow.

Any thoughts as to why this would happen or why I'm getting that particular error message?

Note: I am using Visual Studio 2015 and TFS 2015.

Upvotes: 0

Views: 752

Answers (1)

PatrickLu-MSFT
PatrickLu-MSFT

Reputation: 51103

Since you haven't changed 'anything' to the default TfvcTemplate.12.xaml . You can try to download a new TfvcTemplate.12.xaml without opening it in the XAML visual editor. Just checking in the source control.

If still build fails then Try to clean TFS cash and VS cash

  1. Clean the Cache folder on client computer. The folder path is: C:\Users\username\AppData\Local\Microsoft\Team Foundation\3.0\Cache.
  2. Clean the Cache folder on Server machine. The folder path is: C:\ProgramData\Microsoft\Team Foundation\Web Access\Cache

If build success without error, this may caused by VS. Try to reinstall Visual Studio.

Upvotes: 0

Related Questions