Donovan Brown

Technology Blog

Team Foundation Build Configuration - HTTP code 500

18 April 2013 Donovan-Brown Work (0)
Problem:  After adding host headers to my TFS Website in IIS my build server fails to connect with the following error:   Solution: Add multipleSiteBindingsEnabled=true  to the serviceHostingEnvironment element in the C:\Program Files\Microsoft Team Foundation Server 11.0\Application Tier\Message Queue\web.config file on the application tier machine. Explanation: We added host headers to the TFS Website so users would not have to type in the port to reach web access.  After doing so our build would continue to fail.  Updating the web.config corrects the error and allows builds to run.

Cannot register assembly during Team Build (and I don't want too)

06 February 2013 Donovan-Brown Work (0)
Problem: I have a solution that contains a project with the "Make assembly COM-Visible" checked and I get the following error when I attempt to run a team build: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (3885): Cannot register assembly "C:\Builds\1\TeamProject\Libraries - CI\bin\Debug\Mydll.dll" - access denied. Please make sure you're running the application as administrator. Access to the registry key 'HKEY_CLASSES_ROOT\Mydll' is denied. Solution: Pass "/p:RegisterForComInterop=false" to MSBuild using the MSBuild Arguments process parameter of your build definition. Explanation: The service account running my build agent is not an adminstrator on my build.  Therefore; it does not have permissions to write to the registry to register the COM assembly.  Because this is my build machine I have no desire to have the COM assembly registered on this machine. I simply what the solution to build. When the "Make assembly COM-Visible" is checked the project file is changed to include a target to register the assembly. That target has a condition testing if RegisterForComInterop is true.  By passing the values to MSBuild you are overriding the default value of True with False.  This will allow the project to compile and skip the step to register.

I don't trust 2012 Auto merge but it does it automatically.

31 January 2013 Donovan-Brown Work (0)
Problem: I would like a chance to review the changes before having Visual Studio 2012 automerge my files. Solution: Disable the "Attempt to automatically resolve conflicts when they are generated. Explanation: When Visual Studio 2012 is installed it defaults with this option set. If you uncheck this box Visual Studio behaves as it did in the 2010 version.  You are presented the Conflict Resolution window with options to AutoMerge, Merge Changes In Merge Tool, Take Server Version or Keep Local Version.

I can't create a new backup plan in TFS 2012 after a hardware migration.

24 October 2012 Donovan-Brown Work (0)
Problem I upgraded my TFS from 2010 to 2012 and moved to new hardware after my 2010 machine crashed. When I attempt to setup a new backup plan using the 2012 Power Tools I get the following error: A backup plan already exists for this TFS system on a different machine Solution Connect to SSMS and create a new query using Tfs_Configuration and execute the following command. EXEC sp_dropextendedproperty @name = 'TFS_BACKUP_PLAN_CONTROLLER' Explanation The database has an extended property that it stores the name of the machine used for the backups. This was set while running on the original hardware. You have to remove this value before the power tool will allow you to configure a new backup.

All my workspaces are missing!

24 August 2012 Donovan-Brown Work (0)
Normal 0 false false false EN-US X-NONE X-NONE /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin-top:0in; mso-para-margin-right:0in; mso-para-margin-bottom:10.0pt; mso-para-margin-left:0in; line-height:115%; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;} Problem: After a TFS server move all my workspaces are missing. Solution: Use the TF.exe Workspace command with the /newowner option. Explanation: During a recent TFS upgrade and migration from TFS 2010 running in workgroup mode to TFS 2012 on a new server I lost all my workspaces.  From the new TFS server I could run the TF.exe workspaces command and see all the existing workspaces.  However, if I were to open Visual Studio on any of the client machines none of those workspaces would show up. When TFS is in workgroup mode user accounts are all local accounts.  On the TFS server there was for example a Donovan L Brown account.  The name would be in the format of ComputerName\UserName.  After I moved to new hardware the computer name was different.  However, all the workspaces were owned by the accounts with the old computer name.  You can confirm that by running the TF.exe workspaces command and looking at the owner column. My goal is to simply update the owner of the workspace to point at the new local Donovan L Brown account on the new computer.  tf workspace [/collection:TeamProjectCollectionUrl] [workspacename[;workspaceowner]] [/newowner:ownername] If you have pending changes in the workspaces you will have to shelve them first.  This can be a bit of a challenge as well because you are not the owner of the workspace yet.  To work around this just use the TF.exe workspace command to change the workspace to public.  After which you can shelve the changes using your new account.  Once the changes are shelved you can change the workspace owner to the new account. Finally you can unshelve your changes and return to work.