StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>first let me first ask one question. At the top of the post you write: "My goal is to be able to produce a changelog between APP_A_1.3 and APP_A_1.2."</p> <p>but then when you write what changes specifically you are looking for you list: changesets applied on APP_A_1.2 branch itself changesets applied on APP_A branch before APP_A_1.2 was created changesets applied on Main trunk 1.2 branch before it has been merged to APP_A changesets applied on Main trunk branch before Main trunk 1.2 was created</p> <p>This is not a valid list because it will give you all changes that contributed to APP_A_1.3, APP_A_1.2, 1.1 and so on to the beginning of the repository.</p> <p>I'm not able to test my approach right now, but this is what I would do: - QueryHistory to get all changes checked in directly into branch 1.3 - use QueryMergesExtended to follow merges into this branch. QueryMergesExtended (http://msdn.microsoft.com/en-us/library/ff736485.aspx) was added in TFS 2010 specifically to be much more performant and robust than QueryMerges and QueryMergesWithDetails, in order to support branch visualization tools - afaik you don't need to specify option FollowRenames in QueryMergesExtended because you query merges on the root of the branch - when you get list of source changes (from APP_A) you need to check each changeset to see of it contains merge changes. If so, you need to query merges on app_a for those changesets. Do so recursively until you walk whole branch hierarchy.</p> <p>On the side topic, you can look later at the QueryMergeRelationships (<a href="http://msdn.microsoft.com/en-us/library/microsoft.teamfoundation.versioncontrol.client.versioncontrolserver.querymergerelationships.aspx" rel="nofollow">http://msdn.microsoft.com/en-us/library/microsoft.teamfoundation.versioncontrol.client.versioncontrolserver.querymergerelationships.aspx</a>) which gives you branch object list introduced in tfs 2010 (this is what happens when in Source Control Explorer you select folder and click Convert to branch). However if you can discover your branch in different way (hardcode them) than it's not needed.</p> <p>Hope this helps!</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload