Patrick,
I think this is the API you will need to use: Public Function QueryMerges <http://www.aisto.com/roeder/dotnet/Default.aspx?Target=code://Microsoft .TeamFoundation.VersionControl.Client:8.0.0.0:b03f5f7f11d50a3a/Microsoft .TeamFoundation.VersionControl.Client.VersionControlServer/QueryMerges(S tring,Microsoft.TeamFoundation.VersionControl.Client.VersionSpec,String, Microsoft.TeamFoundation.VersionControl.Client.VersionSpec,Microsoft.Tea mFoundation.VersionControl.Client.VersionSpec,Microsoft.TeamFoundation.V ersionControl.Client.VersionSpec,Microsoft.TeamFoundation.VersionControl .Client.RecursionType):Microsoft.TeamFoundation.VersionControl.Client.Ch angesetMerge%5b%5d> (ByVal sourcePath As String <http://www.aisto.com/roeder/dotnet/Default.aspx?Target=code://mscorlib: 2.0.0.0:b77a5c561934e089/System.String> , ByVal sourceVersion As VersionSpec <http://www.aisto.com/roeder/dotnet/Default.aspx?Target=code://Microsoft .TeamFoundation.VersionControl.Client:8.0.0.0:b03f5f7f11d50a3a/Microsoft .TeamFoundation.VersionControl.Client.VersionSpec> , ByVal targetPath As String <http://www.aisto.com/roeder/dotnet/Default.aspx?Target=code://mscorlib: 2.0.0.0:b77a5c561934e089/System.String> , ByVal targetVersion As VersionSpec <http://www.aisto.com/roeder/dotnet/Default.aspx?Target=code://Microsoft .TeamFoundation.VersionControl.Client:8.0.0.0:b03f5f7f11d50a3a/Microsoft .TeamFoundation.VersionControl.Client.VersionSpec> , ByVal versionFrom As VersionSpec <http://www.aisto.com/roeder/dotnet/Default.aspx?Target=code://Microsoft .TeamFoundation.VersionControl.Client:8.0.0.0:b03f5f7f11d50a3a/Microsoft .TeamFoundation.VersionControl.Client.VersionSpec> , ByVal versionTo As VersionSpec <http://www.aisto.com/roeder/dotnet/Default.aspx?Target=code://Microsoft .TeamFoundation.VersionControl.Client:8.0.0.0:b03f5f7f11d50a3a/Microsoft .TeamFoundation.VersionControl.Client.VersionSpec> , ByVal recursion As RecursionType <http://www.aisto.com/roeder/dotnet/Default.aspx?Target=code://Microsoft .TeamFoundation.VersionControl.Client:8.0.0.0:b03f5f7f11d50a3a/Microsoft .TeamFoundation.VersionControl.Client.RecursionType> ) As ChangesetMerge <http://www.aisto.com/roeder/dotnet/Default.aspx?Target=code://Microsoft .TeamFoundation.VersionControl.Client:8.0.0.0:b03f5f7f11d50a3a/Microsoft .TeamFoundation.VersionControl.Client.ChangesetMerge> () Declaring Type: Microsoft.TeamFoundation.VersionControl.Client.VersionControlServer Assembly: Microsoft.TeamFoundation.VersionControl.Client, Version=8.0.0.0 Regards, William Bartholomew From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Patrick Green Sent: Friday, 14 December 2007 3:30 PM To: [email protected] Subject: RE: [OzTFS] Merging of changeset to new branch. Unable to get details of merged from changesets. I found this entry which probably describes my problem better. Changesets, work items and merging We are hoping to link changesets to work items whenever possible so as to preserve a history as to why/when code was changed. However, I'm finding that when this is done in a branch and then a merge is completed, the merge process does not move this historical information to the target (i.e. the changeset/workitem information is only accessible through the branch).Is there some way to get this information moved to the target when merging? Or is there at least a way to roll up all the source changeset information so that they at least show in the 'merge' changeset on the source? Thanks, Marty Thanks William for the response, you may be right. I actually have a tool to get all the changesets and workitems attached between labels etc, this was great on the mainline, but then after we branched and started merging changesets to the new branch, suddenly no references were left, I cant even see how you could tell where the branch came from. Pat ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of William Bartholomew Sent: Friday, 14 December 2007 4:10 PM To: [email protected] Subject: RE: [OzTFS] Merging of changeset to new branch. Unable to get details of merged from changesets. Patrick, This is a problem I've come across while trying to do exactly the same thing, although I haven't got around to actually doing it yet there are two solutions I can see: 1. Creating a merge tool that carries across the comment and work item information. We considered creating one that allows you to merge based on work items rather than changesets. 2. Use the TFS Version Control API to follow the history back across the branches. William Bartholomew From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Patrick Green Sent: Friday, 14 December 2007 1:58 PM To: [email protected] Subject: [OzTFS] Merging of changeset to new branch. Unable to get details of merged from changesets. We currently have a Mainline which is branched to Release. When I merge a changeset from Mainline to release the information from the original changeset(Comments, WorkItems etc) are not shown or referenced in the new changeset in the Release Branch. I would like to be able to generate ReleaseNotes by doing a changeset/workitem query on the Release branch, but because the work was carried out in Mainline and merged selectively to Release, and the information doesn't seem to come across, I cant get this info. Does anyone know if this can be done? Or of any alternative to know if the status of the Mainline Changeset would show that it was merged to release? Regards Patrick Green OzTFS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. View the web archives at http://www.mail-archive.com/[email protected]/ Powered by mailenable.com, supported by www.readify.net OzTFS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. View the web archives at http://www.mail-archive.com/[email protected]/ Powered by mailenable.com, supported by www.readify.net OzTFS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. View the web archives at http://www.mail-archive.com/[email protected]/ Powered by mailenable.com, supported by www.readify.net OzTFS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. View the web archives at http://www.mail-archive.com/[email protected]/ Powered by mailenable.com, supported by www.readify.net
