Buck Hodges

Azure DevOps (formerly VSTS and Team Foundation Server)

Beta 3 known bug when comparing large files: “Invalid access code (bad parameter).”

In the forum, Carl Daniel reported getting the message "Invalid access code (bad parameter)" when comparing two different versions of a file in Team Foundation Source Control Beta 3.Unfortunately this is a bug that was discovered and fixed after beta 3 was released.  The problem is that large files (on the order of 500K) will crash the ...

SQL error in get with beta 3

On the forum, a couple of users have run into this issue with get, so I thought I would mention it here.There's a known issue in beta 3 where mapping a server path to a local path that exceeds the NTFS limit results in a SQL error message.  The RTM code will give you a nice message to that effect rather than the SQL error ...

Ed Hintz has started blogging

Ed Hintz has started blogging with a post that describes some of the differences between working with SourceSafe and working with TFS.  Ed's the dev lead for the source control client team and is the person to whom I report.  So, check it out and be sure to let him know about the things you do and don't like in the TFS source ...

TFS version control command line: tf.exe

For folks who like command lines or those who've found the typical command line experience a little spartan, you should try tf.exe.One interesting feature of our command line is that it uses dialogs for a number of commands when you are running it interactively (i.e., you don't specify /noprompt or /i).  For instance, you get the same ...

Using Source Code Control in Team Foundation

Chris Menegay's article on MSDN, Using Source Code Control in Team Foundation, provides a good overview of some of the major features. As a part of Visual Studio 2005 Team System and the new Team Foundation Server, Microsoft is providing a true enterprise-class source code control system. Team Foundation Version Control (TFVC) is provided as ...

The 10,000th Changeset

Back on July 13, I wrote about the dates of changeset "milestones" in our dogfood system.  Today we hit changeset 10,000.  The time between 9000 and 10000 was longer than usual because of check-in restrictions in place leading up to beta 3 (bug fixes had to be individually reviewed and approved in ask mode).Here's the full list...