Release management in Team Foundation Server 2013

Microsoft has recently acquired the InRelease release management product from InCycle Software. With the acquisition of InRelease, it fills an important gap that can really slow down teams. InRelease is a great solution that’s been natively built to work well with Team Foundation Server 2013. The following are some screenshots of the InRelease release management product in action:



Are there any changes to the system requirements since Team Foundation Server 2012 (with or without Update 1, Update 2, or Update 3?

The answer is “Yes”. The Team Foundation Server 2013 hardware requirements have remained the same, but there are new software requirements. The most notable ones are that Team Foundation Server 2013 now requires Windows Server 2008 R2 and higher as well as SQL Server 2012 Service Pack 1 (Cumulative Update 2 recommended) and higher. Microsoft no longer supports Windows Server 2008, SQL Server 2008 R2, or SQL Server 2012. If you want to use SharePoint, the new requirements will be SharePoint 2010 and higher.

Part 2: What applications work with the standalone collector?

Currently, the following are only applications that work with the standalone collector:

1) ASP.NET Web applications hosted on Internet Information Services version 7.0, 7.5, and 8.0
2) SharePoint 2010 and SharePoint 2013 applications
3) Managed desktop applications (.exe files)

Part 1: Collect IntelliTrace data with the standalone collector

You can use the standalone collector to save diagnostic data to an IntelliTrace log file (.iTrace file) to debug applications in development or other environments. This lets you record what happened in your app without installing Visual Studio or changing your app’s environment.

The requirements for the standalone collector are:
1) .NET Framework 3.5, 4, or 4.5.
2) Visual Studio Ultimate on a development computer to open the .iTrace files generated by the standalone collector.
3) Matching source files and symbol files to debug with IntelliTrace and step through code.

Unable to format USB drive in NTFS format – Error message “Windows was unable to complete the format”

By default, Windows provides the option to format a USB flash drive with FAT or FAT32 file systems only, but not with NTFS (New Technology File System). The reason behind this is that there are some disadvantages of NTFS usage in this case. First of all, the speed of saving on the flash drive decreases (but the speed of reading data from the drive is the same), and you have to be more careful to always remove the USB flash drive safely.

However, you can still format the Flash Drive in the NTFS format. Follow these steps to format the flash drive in NTFS format:
1. Insert the USB flash drive into the USB port.
2. Click Start, type devmgmt.msc in the Search textbox and press Enter.
3. Find Disk Drives and expand it.
4. Find the USB flash drive you want to format, and double-click it. It opens the Properties dialog box.
5. Click Policies tab.
6. By default, the Optimize for quick removal option selected, switch it to Optimize for performance and then press OK.
7. Now open Computer. Right click on the USB Flash Drive and select Format. The Format dialog box now appears.
8. Select NTFS in the File System field.
9. Press Start and wait while the process will be completed.
10. Now your USB Flash Drive is formatted with NTFS format.

Team Room in Team Foundation Server 2013 and Team Foundation Service

“Team Room” is a new feature of Team Foundation Server 2013 and Team Foundation Service. A “Team Room” is a virtual room where team members can communicate with each other. The logs are saved by date and this way all important direct communication is there also for later dates.

Does Team Foundation Server 2013 Preview supports side-by-side installation with Team Foundation Server 2010?

Unfortunately, this is not supported. The installation process for the Team Foundation Server 2013 Preview will automatically uninstall Team Foundation Server 2010 (with or without Service Pack 1).