Peder Rice

We have old XAML build scripts that prompt the developer to choose which branch to publish. As far as I can tell, the new build system does not provide this...

In a nutshell, we need the ability to change which branch we're building from, just like Git repositories have: 

As far as CI goes, I haven't seen how teams manage to combine CI+TFVC+Feature Branching without creating new build scripts for each feature branch.

Hey @jessehouwing, have you made any progress on downloading from source control? We're trying to build this out ourselves but running into module- and assembly-loading nightmares in our homegrown PowerShell...

So we ended up writing a script that we call using the PowerShell Task. It downloads files for a selected branch in a new workspace, undoing any local changes before...

I did try that, and I also researched the REST API, which doesn't expose the branch path in their `PATCH` method. I think the only method available is via `UPDATE`...

https://stackoverflow.com/questions/25858650/update-status-of-tfs-builds-with-powershell The examples in this post are likely specific to XAML builds, but there may be a way with PowerShell to change data on a Build object, including the Branch...

@TobiasOetzel , I'm just seeing your comment now about preprocessors, as a colleague of mine stumbled upon an issue using template tags (http://stackoverflow.com/questions/32289904/using-template-schema-in-xml-view). Has anything changed, or is any support...

You might be able to proxy the delete calls and handle the exception. I'm thinking something like set up a generic route `/api/` that routes to `/odata/`, where `/api/` =...

So, I hate myself for this, but I got the exception-handling piece of this wired up. In my `DatabaseDomain.cs` file, I have something like: ``` protected void OnDeletingRelatedDocuments(RelatedDocument entity) {...