Feb 192013
 

Recently, I had to authenticate to Team Foundation Server using an account with greater permissions to perform some administrative tasks.  As you may know, this requires entering alternate credentials when you add the server to the list of TFS servers, or when you need to connect to the server.  Once you’ve connected once, you aren’t prompted again as the credentials are cached locally.

In the past, to remedy this, you could simply delete the local TFS cache, which is located in the following directory (Windows Vista and onwards):

<system drive>\Users\<your profile>\AppData\Microsoft\Team Foundation

image

However, in more recent versions this has changed somewhat, and the user’s credentials are no longer linked to the local TFS cache or configuration.

Where are the Credentials?

Good question.  After some digging about, it seems that the credentials are now stored in the user’s Credential Manager store within Windows.  If you aren’t familiar with this, it was introduced on the more recent versions of Windows, and it lives via the Control Panel, under the following path: Control Panel->User Accounts

image

Inside this location, you can view all the locally cached credentials, including Windows Credentials:

image

Note: that it appears that for TFS credentials used by Team Explorer and other applications, the credentials are the ones under “Generic Credentials” not under “Windows Credentials” (in case you have TFS entries in both).

Making Changes

To modify or remove the credentials you use to connect to TFS, simply expand the appropriate entry and click on “Edit”, or to delete the local credentials, click on “Remove”.  If you opt to remove the credentials, you’ll be prompted to enter new credentials next time you connect to the specified TFS server.

image

 

So that was a little out of the way. When I tested this, I made sure that I’d disconnected from TFS before changing/removing the credential configuration.

It would be nice if Team Explorer linked to the Credentials Manager so we didn’t have to go digging to work this out, wouldn’t it?

Aug 172012
 

It’s been a massive week for Microsoft.  We are really in full swing when it comes to the largest release cycle in Microsoft’s history.

It all began on Wednesday at 10 AM PST (Pacific) which is an appallingly wee-hours 3 AM AEST (Australian East).  Insomnia had gripped me, so with a glance at the clock, I decided to stumble online.  Just on the release time, my machine decided that it had to reboot owing to a security patch.

By the time the damned thing rebooted it was too late – MSDN/TechNet were being pummelled by eager subscribers all intent on downloading the RTM ISOs.  I simply couldn’t get launch an Akamai download.

In the end I had to wait until yesterday afternoon, when the queue had died down.  There is quite a lot to digest, including the dark horse, Team Foundation Server 2012.  Word on the grapevine is that Windows Server 2012 will also go RTM shortly as well.

There are quite a number of considerations confronting the subscriber – platform (x86 or x64), locale (US or UK English?), license (Retail, VL, MSDN) and flavour (Win 8 or Win 8 Enterprise, Visual Studio Ultimate/Professional or Premium?).  As one friend put it to me: “What’s the difference?”

For a good look at the differences, here are some helpful links:

Compare Flavours of Windows 8

Compare Editions of Visual Studio 2012

Noting that Windows 8 Enterprise has the features of Windows Pro but has extra support for large organizations.

There are also quite a few additional installation packages to compliment Visual Studio 2012 including the Test Agents (which I’ve mentioned in previous articles to do with establishing load testing), Intellitrace Collector, Remote Tools and the ever handy TFS Everywhere.

Once Windows Server 2012 joins the fray, we will have a very busy period indeed.  Much to write about, so little time.  You’ll also hear from me (with no undue level of verbosity) as I blog live from Microsoft Australia’s annual tech-fest, TechEd 2012 which is on the Gold Coast this year.

Enjoy the new releases and check back here for more, as I begin my long journey diving into the latest tech.

Jun 022012
 

Introduction

Following on from the previous article, where I installed the Visual Studio 11 Release Candidate on a Windows 8 Release Candidate, I’m now going to step through the process to set up a complimentary ALM capability – Team Foundation Server 2012 (Release Candidate).

As per the previous article, links to the downloads for all products mentioned are listed in the following article.

Preparation

I’ve installed a copy of the Windows Server 2012 (Datacenter) Release Candidate as the host for my TFS installation.  This configuration will not support SharePoint Foundation 2010 – so this is not a recommended configuration if you want to use Team Projects/Team Sites.

As I was preparing to install TFS, I copied the .ISO files across from my SAN, and noticed something interesting on Windows Server 2012 RC – the file copy dialog reveals a lot more information on the progress of the file copy operation:

file-copy

Once you have mounted and run the initial TFS 2012 RC installer, there is an initial configuration of the base setup files, followed by the TFS configuration screen.

initial-screen install-screen

The initial option is to display the “Standard Single Server” configuration option:

config-choice

Pre-installation

I’ve pre-installed SQL Server (so I can add reporting services later), but I’m going to use the “Basic” TFS configuration, since I won’t have SharePoint configured.  If you also want to pre-install SQL Server, the configuration you are likely will require is per the below screenshot:

sql

Once again, it is always a good idea to familiarise yourself with the TFS prerequisites which can be found in the TFS install guide which is found in the root of the TFS disc.

The Basic Configuration

Anyhow, continuing onwards – as I mentioned earlier, I’m picking the “Basic” configuration (I’ll do a series of articles on setting up a complete solution once Team Foundation Server 2012 goes RTM).

config-choice-basic

This leaves us with very few things to configure.  Literally, all I need to do is decide whether I’ll let the installer use SQL Server Express, or to point at an existing SQL Server instance.

basic-config

The configuration is verified, and once you hit the “configure” button, the configuration is executed:

installing verifysuccess

Finished!

When the configuration is complete, you should be able to connect to TFS from Visual Studio 11 directly (no need to install Team Explorer separately!).  In my case, I connected as an Administrator, but you would obviously want to create some users and groups.

connectconnected

In the next article

Now that we have Visual Studio 2012 connected to TFS 2012, we can create a Team Project and begin a project!  I’ll go back and establish Reporting capabilities in a later article.

Jun 012012
 

Today was a big day if you happen to enjoy Release Candidate builds from Microsoft.  Not only did we see the RC release of both Windows 8 and Windows Server 2012 (and Hyper-V Server), but it also coincided with the release of RC editions of the Visual Studio 11 developer platform (including Team Foundation Server, Test Manager and Test Agent packs).

Naturally, releasing such a wide range of products simultaneously means there’s a whole lot of ground to cover.  I naturally like to whet my appetite across client OS, server and developer tools in equal measure – but this is going to be some effort this time around!

I’ve been looking ahead at the changes expected in the Visual Studio 11 RC already – and there figures to be a lot of discussion around the changes to the VS user interface, especially when compared to the beta.  I’m also going to focus on the changes in .NET 4.5 and what we can expect in the RTM versions.

It looks like you can suppress the ALL CAPS menus in Visual Studio 11 RC with a registry key – props to MVP and scrum fiend Richard Banks for the tip.

HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\11.0\General\SuppressUppercaseConversion
REG_DWORD value: 1

Lastly.. Windows 8 RC.  In my experience, the RC is very close to the RTM edition, so we’ll be expecting this release to be something you could run on bare metal.  Same goes for Windows Server 2012.

I sincerely wish I had the money to outlay for a new server-spec machine, as I’d be extremely keen to give the new Hyper-V Server 2012 a run on bare metal.  I’ve been hearing very, very good things about the upcoming release and how Hyper-V has overcome some of the annoying limitations of the previous version.

Anyhow – here are links to the downloads.  If you enjoy Microsoft RC products, start your downloading! 

/Rob

Links

Windows 8 RC 1

http://windows.microsoft.com/en-US/windows/home
http://windows.microsoft.com/en-US/windows-8/download?ocid=W_MSC_W8P_DevCenter_IE_EN-US

Windows Server 2012 Datacenter RC 1

http://technet.microsoft.com/en-us/evalcenter/hh670538.aspx?ocid=&wt.mc_id=TEC_108_1_33

Visual Studio 11 RC 1/
Team Foundation Server 2012 RC 1

http://www.microsoft.com/visualstudio/11/en-us/downloads