In beta 3 (including refresh) and earlier, work items have always been assigned to user names. For some organizations, that’s a real problem, as the user names do not have any relationship to the user’s real name. We have fixed this for RTM.
James Manning today pointed out a post from Marcel de Vries showing how to register for email when someone checks in after overriding a policy failure. While any policy failres and override comment are included in the standard check-in email, this allows you to get an email specifically when someone overrides a policy failure.
Beta 3 of TFS has now been released and should be available on MSDN today (or very soon :-). The differences between beta 3 and beta 3 refresh are small for most things. Jeff Beehler wrote about some of the beta 3 refresh differences two weeks ago.
I had mentioned in my September 10th post on file type detection that you couldn’t change the encoding on a pending add, without undoing the add and re-adding it. While it won’t work in beta 3 or beta 3 refresh, you’ll be able to change the encoding on a pending add in the next public release.
Have you wished that the output of the dir command from tf.exe would show you the dates and sizes of the files like cmd.exe’s dir command? Even though tf.exe won’t do that in version 1, the version control API provides the call necessary.
Unfortunately, there’s not a fast, efficient way to see the list of labels in the system with the full comment without also seeing a list of all of the files included in a label. You also can’t efficiently answer the question, “What labels involve foo.cs?”
If you want to learn more about web load testing in VSTS, you’ll want to check out Ed Glas’ webcast on Tuesday, Oct. 25. Brian Harry has been using VSTS load testing developed by Ed’s group to answer the question, “How many users will your Team Foundation Server support?”
The beta 2 Virtual PC image was hugely popular. The new Team Foundation beta 3 VPC image is now making its way up to MSDN. So, later today or Monday you’ll be able to download and run a single-server and client beta 3.
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.
You can find the latest dogfood statistics on Brian’s blog.
[Update 10/12] John Lawrence also has the statistics as usual, including Excel charts. I saw Brian’s, and I didn’t think to check there.