Here are the screenshots from upgrading a TF Build from 2012 to 2013.2:
Good luck!
–Neno
Tags:
Tags:
Meanwhile I updated most of my tools for TFS 2013. Here’s a list:
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:
Download all TFS Build Tools as .ZIP file: TfsBuildTools.zip
Let me know if you find them useful!
–Neno
Tags:
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)
–Neno
Tags:
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:
You do not need the Test Attachment Cleaner if you:
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:
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:
Good luck!
–Neno
Tags:
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:
The Problem
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
–Neno
Tags:
The Problem
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:
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.
- 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
- Removed the references to your Office interop assemblies and add references to the assemblies in your libs folder.
–Neno
Tags: