Visual Studio Online (VSO) vs. Team Foundation Server (TFS)

This blog post is comparing the current feature set of Microsoft’s hosted TFS solution – Visual Studio Online (VSO) and the on-premises Team Foundation Server product.

Feature Comparison (as of February 2014)

 

TFS

VSO

Work Items, Version Control, & Build

Yes

Yes

Agile Product/Project Management

Yes

Yes

Test Case Management

Yes

Yes

Heterogeneous Development (Eclipse, Git)

Yes

Yes

Ease of Installation and Setup

+/-

++

Collaborate with anyone, from anywhere

+/-

++

Data stays inside your network

Yes

No

Process Template & Work Item Customization

Yes

No

SharePoint Integration

Yes

No

Data Warehouse & Reporting

Yes

No

CodeLens Support

Yes

No

Cloud Load Testing

No

Yes

Application Insights

No

Yes

Always running the latest version of TFS

No

Yes

Remember: Visual Studio Online is currently a so-called “commercial preview”.

Some other limitations of VSO (as of February 2014)

  • No Data Export (there are plans to make it available for a short time period)
  • No Data Import (if you want to move from on-premises TFS to VSO)
  • No Integration with Active Directory (users sign in using Microsoft Accounts)
  • No choice of geographic location (data stored in data center in Chicago)

–Neno

When to use the Test Attachments Cleaner (and when not)

What is the Test Attachment Cleaner?

A command line tool that only removes the attachments. It does not touch the test runs, which contain the pass/fail data. So, running Test Attachment Cleaner will not impact the record of the test runs.

You need to Test Attachment Cleaner if you:

  • Do manual test runs and want to delete attachments without deleting the test runs
  • Do automated test runs and want to delete attachment for builds which have been deleted already, but the build definition’s retention policy was not set to delete “test results” (because this is turned off by default)

You do not need the Test Attachment Cleaner if you:

  • Have automated test runs triggered by a build, and you have configured the build definition’s retention policy to delete “test results” (which is not set by default)
  • Delete the Test Runs manually (as this deletes the attachments)

Where do I get it from?

The Test Attachment Cleaner is available as part of the TFS Power Tools:

(Thanks Ravi Shenker from Microsoft for the input!)

SOLVED: TF221122: Error While Processing TFS OLAP Cube

The Problem

After upgrading to TFS 2013, the TFS OLAP Cube fails processing with one of the following messages:

Invalid column name ‘System_AssignedTo__Name’.; 42S22;

Invalid column name ‘System_AssignedTo__SID’.; 42S22

Query execution failed for dataset ‘ds[Whatever]’

The Solution

Found in Jeff Hunsaker’s blog post:

  1. In TFS Admin Console, look up the account under “Account for accessing data sources” under the “Analysis Services” tab (Reporting » Edit).
  2. In SQL Server, add that account to the Tfs_Warehouse database, to the TFSEXECROLE role.

Good luck!

–Neno

SOLVED: Error ‘(405) Method Not Allowed’ when publishing a NuGet package to a NuGet server

The Problem

When trying to publish NuGet Packages to a NuGet server you get the error message:

Failed to process request. 'Method Not Allowed'.

The remote server returned an error: (405) Method Not Allowed.

The Solution

Found in this post on stackoverflow.com:

When you LIST packages in NuGet server you point to http://nugetserver.com/nuget. However when you are trying to PUSH or DELETE a package you need to point to http://nugetserver.com without the nuget folder in the path.

Good luck!

–Neno