Team Foundation Build Configuration - HTTP code 500

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.

I exceeded the maximum size for upload in SharePoint

Problem: I get a size limit error when I try to upload a document to SharePoint. Solution: By default the maximum size is set to 50 MB. We simply need to increase the acceptable file size. Explanation: In Central Administration, in Application Management, click Manage web applications. Select the application (for example, SharePoint - 80). On the Web Applications ribbon, click the down arrow on the General Settings button. Click General Settings. Scroll to Maximum Upload Size. Set the property to the same number as the Maximum Workbook Size in Excel Services. Click OK.

Web application causes An attempt was made to load a program with an incorrect format error.

Problem: When I attempt to start my web application running in IIS 8 I receive the following error: Could not load file or assembly 'Xxx' or one of its dependencies. An attempt was made to load a program with an incorrect format. Solution: Enable 32-Bit Applications for the Application Pool running your application. Explanation: Start IIS and select your web applications virtual directory under Sites\Default Web Site. Select Basic Settings from the Actions pane.  Note the Application pool your application is using and click Cancel to close the dialog.  Select Application Pools from the Connections pane.  Right click on the application pool running your web application and select Advanced Settings from the context menu.  Change Enable 32-bit Applications from False to True.

How to connect Office 2003 to TFS 2012

Problem: Team Explorer 2012 does not integrate with Office 2003. Solution: Install Team Explorer 2008, Visual Studio 2008 SP1 and 2008 Compatibility Update. Explanation: This procedure will also work to get Visual Studio 2008 connected to TFS 2012. If you open Excel 2003 after installing Team Explorer 2012 you may get an error when you exit Excel. Just click Close the program. The next time start Excel you will be presented the following error: Click Yes to disable the 2012 version of the ‘team foundation add-in’ and close Excel. Now you will have to execute a few commands from an elevated command prompt. From an admin command prompt, change directories to “Program Files\Microsoft Visual Studio 9\Common7\IDE\PrivateAssemblies” or “Program Files (x86)\Microsoft Visual Studio 9\Common7\IDE\PrivateAssemblies” on a 64 bit machine. To register the 2008 version of the add-in run the following command and press Enter: regsvr32 TFSOfficeAdd-in.dll Now when you open Excel you will see a new Team menu.

I get an error trying to run reports on TFS2012 install

Problem: I get the following error when I attempt to view reports: An error has occurred during report processing. (rsProcessingAborted)Cannot impersonate user for data source 'TfsReportDS'. (rsErrorImpersonatingUser)Log on failed. Ensure the user name and password are correct. (rsLogonFailed)For more information about this error navigate to the report server on the local server machine, or enable remote errors  Solution: Verify that the password for the account reporting services is using has not expired. Explanation: In your browser, navigate to http://localhost/reports (from your reporting server machine).Click on Tfs2010ReportDS on the home page. Under the 'Credentials stored securely in the report server' click the Test Connection button. You should see the following message "Log on failed. Ensure the user name and password are correct."Simply reenter the username and password information and test the connection again.

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

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.

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.

How do I convert a Web Site to a Web Application

Problem: We created our application using the Web Site project template and would like to change to a Web Application. Solution: Explanation: Just don't use Web Sites! Why would I want my source code (all of my IP) on a server that could be compromised? They also do not play nice with source control systrems or automated build.

I want xml transforms to happen on build instead of only publish.

Problem: I have xml transforms I want to preform on build not only on publish. I also want an easy way to transform my config files during my team build.  Finally I want to use it on app.configs in WPF applications as well. Solution: Use SlowCheetah XML Transforms package.  You can install it from the Extension Manager in Visual Studio.  Explanation: SlowCheetah enables you to transform your app.config or any other XML file based on the build configuration. It also adds additional tooling to help you create XML transforms.