This information does not apply to the WebHooks version.
The TFS Aggregator works with the following versions of TFS:
The installer will detect the correct TFS version and will install the appropriate binary. If you’re upgrading, please uninstall your current TFS Aggregator version, upgrade TFS, then run the installer to automatically install the matching version.
The TFS Aggregator plugins writes to Windows Event log critical errors; the TFSAggregator Source must be defined in the Application log. The MSI takes care of this.
The TFS service account must have permissions to change your work items (on behalf of others if you have enabled impersonation).
Download TFSAggregator MSI file from the latest Release.
Unblock the downloaded file.
Launch the installer and accept the license
The MSI packages all three Aggregator flavors, one for each supported TFS version. The installer detects the TFS version installed and deploy the correct assemblies.
The installer detects automatically the TFS version: it fails if TFS is not present.
It will install under %ProgramFiles%
, typically C:\Program Files\TFS Aggregator
, three folders: bin
, docs
and samples
.
Furthermore it installs the plugin in the proper directory — for TFS 2015 can be C:\Program Files\Microsoft Team Foundation Server 14.0\Application Tier\Web Services\bin\Plugins
— the plugin assemblies and the default no-op Policy file samples\TFSAggregator2.ServerPlugin.policies
.
> An existing Policy file is not overwritten.
In the samples
folder you will find two Powershell scripts to install or remove Aggregator in case the TFS Administrator does not want (or can) use the MSI file.
The scripts require an elevated Powershell prompt.
To configure Aggregator you must add new rules in the policy file.
TFSAggregator2.ServerPlugin.policies
file.TFSAggregator2.ConsoleApp.exe
command line toolC:\Program Files\Microsoft Team Foundation Server 14.0\Application Tier\Web Services\bin\Plugins
See Console Application for more information on using the command line tool.
Due to the fact that there have been breaking changes between TFS Server Object Model versions, there may be a need to fix the TFS aggregator after an upgrade.
When upgrading from/to specific versions, you need to uninstall TFS aggregator before upgrading the Application Tier server re-install it afterwards.
An uninstall+reinstall is required, repairing may not work. TFS will detect the incompatibility and will not load the plugin if the version mismatches.
TFSAggregator2.ServerPlugin.policies
using one of the provides examples to build your actual policy.
TFSAggregator2.ConsoleApp.exe
command line tool, see TFS Aggregator Troubleshooting.
New-EventLog -LogName "Application" -Source "TFSAggregator"
TFSAggregator2.ServerPlugin.dll
, TFSAggregator2.Core.dll
and TFSAggregator2.ServerPlugin.policies
to the plugin location on the Application Tier of your TFS Servers:
C:\Program Files\Microsoft Team Foundation Server 14.0\Application Tier\Web Services\bin\Plugins
;TFS detects automatically that a file was copied in and will load it in.
You can verify if assembly version matches TFS version using this Powershell code
$pathToAssemblyFile = "C:\Program Files\Microsoft Team Foundation Server 14.0\Application Tier\Web Services\bin\Plugins\TFSAggregator2.ServerPlugin.dll"
[System.Reflection.Assembly]::LoadFile($pathToAssemblyFile).GetCustomAttributesData() | ?{ $_.AttributeType -eq [System.Reflection.AssemblyConfigurationAttribute] } | select ConstructorArguments
Remove the TFSAggregator2.*
files from the plugin location on the Application Tier of your TFS Servers
The plugin folder is usually at this path:
C:\Program Files\Microsoft Team Foundation Server 14.0\Application Tier\Web Services\bin\Plugins
C:\Program Files\Microsoft Team Foundation Server 12.0\Application Tier\Web Services\bin\Plugins