Comments on: Again on assembly numbering during TFS Build http://www.codewrecks.com/blog/index.php/2009/09/07/again-on-assembly-numbering-during-tfs-build/ Wrecks of code floating in the sea of Internet Mon, 06 Sep 2010 12:34:55 +0100 http://wordpress.org/?v=2.9.2 hourly 1 By: alkampfer http://www.codewrecks.com/blog/index.php/2009/09/07/again-on-assembly-numbering-during-tfs-build/comment-page-1/#comment-2922 alkampfer Thu, 28 Jan 2010 18:51:56 +0000 http://www.codewrecks.com/blog/index.php/2009/09/07/again-on-assembly-numbering-during-tfs-build/#comment-2922 Yes you are right :) , GetLatestChangesedId is unique across all project, so this technique cannot be used safely. Thanks a lot for pointing me out this, I'll try as soon as possible to change the sample with a more correct one. :) alk. Yes you are right :) , GetLatestChangesedId is unique across all project, so this technique cannot be used safely. Thanks a lot for pointing me out this, I’ll try as soon as possible to change the sample with a more correct one. :)

alk.

]]> By: Royalsampler http://www.codewrecks.com/blog/index.php/2009/09/07/again-on-assembly-numbering-during-tfs-build/comment-page-1/#comment-2921 Royalsampler Thu, 28 Jan 2010 18:31:07 +0000 http://www.codewrecks.com/blog/index.php/2009/09/07/again-on-assembly-numbering-during-tfs-build/#comment-2921 The idea of using GetLatestChangesetId(); is flawed; This method returns the greatest changeset from the entire team foundation server, and changeset ids are unique across all projects on the server. For example: I make a checkin to my asp.net application and the checkin becomes changeset 123456. I build 20 minutes later and GetLatestChangesetId() returns 123460 because several other projects that I have no control over have had checkins in the time between. My assembly gets versioned with changeset 123460. Later, I need to verify that a certain bug fix is included in my assembly, so i query my history in TFS for changeset 123460, and find that 123460 is not a valid changeset number for my project. The idea of using GetLatestChangesetId(); is flawed; This method returns the greatest changeset from the entire team foundation server, and changeset ids are unique across all projects on the server.
For example: I make a checkin to my asp.net application and the checkin becomes changeset 123456. I build 20 minutes later and GetLatestChangesetId() returns 123460 because several other projects that I have no control over have had checkins in the time between. My assembly gets versioned with changeset 123460. Later, I need to verify that a certain bug fix is included in my assembly, so i query my history in TFS for changeset 123460, and find that 123460 is not a valid changeset number for my project.

]]>