Buck Hodges

Visual Studio Online, Team Foundation Server, MSDN

November, 2013

  • Buck Hodges

    Patch for issue with Visual Studio 2013 Queue Build dialog


    In Visual Studio 2013 and Team Explorer 2013 there is a bug that will cause the “What do you want to build?” combo box to be disabled and the entire Parameters tab to be blank. We have now released a patch to fix this bug: KB 2898341. This bug occurs when using VS or TE 2013 with a TFS 2013 server. We introduced the bug at the very end of the release when we made a performance optimization for builds on the server used by the Developer Division.

    Follow me on Twitter at twitter.com/tfsbuck

  • Buck Hodges

    Visual Studio and Team Explorer 2013 no longer require IE 10 for installation


    When Visual Studio 2013 and Team Explorer 2013 were originally released, the installation process required that Internet Explorer 10 or newer was installed. Today we released updated installers that no longer require IE 10.

    You will get a warning at the beginning of your installation that looks like the screen shot below. For VS 2013 there is a KB article titled Visual Studio 2013: Known issues when IE10 is not installed that describes what the limitations are if you don’t have IE 10 or newer installed (the “some features” link in the dialog takes you to that KB article). The good news is that there aren’t many things that require IE 10.

    TE 2013 will work as you expect without IE 10. There are no limitations for Team Explorer when IE 10 is not installed.

    The updated installers are available from the Visual Studio Download page and from the MSDN subscriber downloads. [Update Nov. 13th: Due to a problem with the update to subscriber downloads, the new bits are only available from the Visual Studio Download page. This will be fixed in the next few days.]


    Follow me on Twitter at http://twitter.com/tfsbuck

  • Buck Hodges

    Updated Team Foundation Server 2013 download addressing web and installation path issues


    Today we have updated the TFS 2013 installation packages both on the web download page and in MSDN subscriber downloads. The reason is that we found two bugs that we wanted to address broadly. We’ve made changes to be able to catch these types of issues in the future.

    Here are details on the two fixes.

    Fixed: Red error box when using Code (version control) in the web UI

    In the case of upgrading from a prior version of TFS to TFS 2013 RTM, you will see a big error box that says “Error in the application” when using the Code section in the web UI (for example, viewing History). The reason is that we had a bug that was introduced shortly before RTM where the version number for the discussion service, which is the back end for the code review feature, is not set correctly (it was left as a 5 and should have been a 6). As a result, what was returned by the server was InvalidServiceVersionException. Users had reported this in a couple of forum threads (here and here) where we had provided a simple SQL script to fix the issue until this updated download was available.


    For anyone who has the original RTM installed (not the new release mentioned above) and has this issue, the fix from Vladimir will correctly address the issue, or you can contact customer support who will be able to help you. You would need to run this SQL script on each collection database. Please do not modify this SQL script or make any other changes to the TFS databases.

                FROM    sys.extended_properties
                WHERE   name = 'TFS_SERVICE_LEVEL'
                        AND value = 'Dev12.M53')
       EXISTS ( SELECT *
                FROM    sys.extended_properties
                WHERE   name = 'TFS_DATABASE_TYPE'
                        AND value = 'Collection')
        EXEC prc_SetServiceVersion 'Discussion', 6

    Fixed: Unable to install into a custom path

    When you install TFS 2013, you do not have to uninstall TFS 2012 – the installer will take care of it for you and preserve your settings and provides a much better experience for upgrading databases compared to a patch. This was a feature we introduced with TFS 2012 specifically for easy installation of the updates for TFS 2012. There was a bug in the original TFS 2013 RTM release where if your installation for your TFS 2012 installation did not have “11” in the path (for example, d:\tfs) that you would not be able to change path and the installation would leave your TFS inoperable if you went forward with the installation (if this has happened to you, contact customer support, and we’ll get it fixed for you).

    For both of these issues, we have learned from them and now have checks in place to catch them in the future.

    Follow me on Twitter at twitter.com/tfsbuck

Page 1 of 1 (3 items)