TFS & Visual Studio ALM – by Neno Loje

(formerly Team System, VSTS)

Screen Gallery: Upgrading TF Build from 2012 to 2013

May 7th, 2014 · No Comments · 18141, Screen Galleries, Team Foundation Build (TF Build), TFS Installation and Configuration, Visual Studio Online

Here are the screenshots from upgrading a TF Build from 2012 to 2013.2:

TFB 2013 Upgrade - 01

TFB 2013 Upgrade - 02

TFB 2013 Upgrade - 03

TFB 2013 Upgrade - 04

TFB 2013 Upgrade - 05

TFB 2013 Upgrade - 06

TFB 2013 Upgrade - 07

TFB 2013 Upgrade - 08

Good luck!

–Neno

Tags:

Screen Gallery: Upgrading TFS 2012 to TFS 2013

May 6th, 2014 · No Comments · 18141, Screen Galleries, Team Foundation Server, TFS Installation and Configuration, Visual Studio Online

Here are the screenshots from upgrading a TFS 2012.3 to TFS 2013.2:

TFS 2013 Upgrade - 03

TFS 2013 Upgrade - 04

TFS 2013 Upgrade - 05

TFS 2013 Upgrade - 04

TFS 2013 Upgrade - 06.2

TFS 2013 Upgrade - 06

TFS 2013 Upgrade - 07

TFS 2013 Upgrade - 08

TFS 2013 Upgrade - 09

TFS 2013 Upgrade - 10

TFS 2013 Upgrade - 11

TFS 2013 Upgrade - 12

TFS 2013 Upgrade - 13

TFS 2013 Upgrade - 14

TFS 2013 Upgrade - 08

TFS 2013 Upgrade - 09

TFS 2013 Upgrade - 10

TFS 2013 Upgrade - 11

TFS 2013 Upgrade - 12

Good luck!

–Neno

Tags:

Updated Tools for TFS 2013

May 5th, 2014 · 5 Comments · Downloads, Tools and Utilities

Meanwhile I updated most of my tools for TFS 2013. Here’s a list:

  • TfsClean.exe – Finds and deletes old and unused workspaces and shelvesets.
  • TfsCreateBuild.exe – Creates “fake” builds in TFS without actually running them.(e.g. can be used to store the build results from a different build system)
  • TfsExport.exe – Download files from TFVC without the need for a workspace, set modified date to last check-in date, and remove VC bindings.
  • TfsMoveDescriptions.exe – Moves text from plaintext or HTML fields to another HTML field (e.g. to copy the work item descriptions to the new System.Description field).
  • TfsRefreshWarehouse.exe – Processes the TFS Data Warehouse and Services Cube.
  • TfsReg.exe – Reads or writes values from/to the TFS registry.
  • TfsSyncIdentities.exe – Foces TFS to synchronize identities with Active Directory.
  • TfsWarehouseController.exe – Allows you to set warehouse settings (like the refresh interval).

The most convenient way to get all the tools is to download this .ZIP file: TfsToolsSuite.zip

But wait, there’s more…

Server-Side Plug-Ins:

Download all event-handlers as .ZIP file: TfsEventHandlers.zip.

TFS Build Tools:

  • CreateZip.exe
  • FtpUpload.exe
  • TfbEnv.exe – Sets additional environment variables for TF Build.
  • TfbNotes.exe – Writes build report to a file.
  • TfbNuGet.exe
  • TfbSetVer.exe
  • VerifyFile.exe

Download all TFS Build Tools as .ZIP file: TfsBuildTools.zip

Let me know if you find them useful!

–Neno

Tags:

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

March 10th, 2014 · 3 Comments · 18290, Team Foundation Server

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

Tags:

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

March 7th, 2014 · No Comments · 18287, Team Foundation Build (TF Build), TFS Administration

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!)

Tags:

SOLVED: TF221122: Error While Processing TFS OLAP Cube

March 6th, 2014 · No Comments · TFS Reporting, Troubleshooting TFS

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

Tags:

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

March 6th, 2014 · No Comments · 18335, Team Foundation Build (TF Build)

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

Tags:

Build fails with missing file: System.Management.Automation.dll

February 14th, 2014 · 1 Comment · Team Foundation Build (TF Build)

The Problem

  • The Build breaks with the following message:

Exception Message: Could not load file or assembly ‘System.Management.Automation, PublicKeyToken=31bf3856ad364e35′ or one of its dependencies. The system cannot find the file specified. (type FileNotFoundException)

The Solution

The Cause

  • You might be using the Community TFS Build Extensions. These include the InvokePowerShellCommand activity, which has a dependency on this .DLL

–Neno

Tags:

Build fails to find GraphCmd.exe (Layer Diagram Validation)

February 14th, 2014 · No Comments · Team Foundation Build (TF Build)

The Problem

  • The Build breaks with the following message:

Error message:
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v11.0\ArchitectureTools\Microsoft.VisualStudio.TeamArchitect.LayerDesigner.targets (148): The "GraphCmd" task failed unexpectedly. System.InvalidOperationException: Cannot start process because a file name has not been provided.

The Solution

Add this xml snippet into all of your Modeling project (*.modelproj) files:
<PropertyGroup>
    <GraphCmdPath Condition="’$(GraphCmdPath)’==” and ‘$(Registry:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\VisualStudio\11.0\Architect@GraphCmdDir)’ != ”">$(Registry:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\VisualStudio\11.0\Architect@GraphCmdDir)</GraphCmdPath>
</PropertyGroup>

–Neno

Tags:

How to compile projects that reference Microsoft.Office.Interop assemblies with a build server

February 13th, 2014 · No Comments · Team Foundation Build (TF Build)

The Problem

A project that references Office interop assemblies (Microsoft.Office.Interop) fails to compile on TF Build (or VSO’s Elastic Build Service).

The error message might be similar to this one:

The type or namespace name ‘Office’ does not exist in the namespace ‘Microsoft’ (are you missing an assembly reference?)

The Solution (based on this forum post)

You want to check-in the interop assemblies.

  1. Create a “Lib” folder and add all relevant assemblies, like:
    • Microsoft.Office.Interop.Word.dll
    • Microsoft.Office.Interop.Excel.dll
    • Microsoft.Vbe.Interop.dll
    • OFFICE.DLL
  2. Removed the references to your Office interop assemblies and add references to the assemblies in your libs folder.

–Neno

Tags: