Downloads of v 9.1.7:


Last Update:

09 Jul 2016

Package Maintainer(s):

Software Author(s):

  • JetBrains


teamcity vstest mstest customlogger unit testing

TeamCity VSTest Custom Logger

  • 1
  • 2
  • 3

9.1.7 | Updated: 09 Jul 2016



Downloads of v 9.1.7:



Software Author(s):

  • JetBrains

  • 1
  • 2
  • 3
TeamCity VSTest Custom Logger 9.1.7

  • 1
  • 2
  • 3

This Package Contains an Exempted Check

Not All Tests Have Passed

Validation Testing Passed

Verification Testing Exemption:

Dependency fails due to requiring input (package parameters). Asking JetBrains to set that to a default of localhost.


Scan Testing Successful:

No detections found in any package files


To install TeamCity VSTest Custom Logger, run the following command from the command line or from PowerShell:


To upgrade TeamCity VSTest Custom Logger, run the following command from the command line or from PowerShell:


To uninstall TeamCity VSTest Custom Logger, run the following command from the command line or from PowerShell:


NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to

4. Choose your deployment method:

choco upgrade teamcity-vstest-customlogger -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:

choco upgrade teamcity-vstest-customlogger -y --source="'STEP 3 URL'"

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0

Exit $exitCode

- name: Ensure teamcity-vstest-customlogger installed
    name: teamcity-vstest-customlogger
    state: present
    version: 9.1.7
    source: STEP 3 URL

See docs at

chocolatey_package 'teamcity-vstest-customlogger' do
  action    :install
  version  '9.1.7'
  source   'STEP 3 URL'

See docs at

    Name: teamcity-vstest-customlogger,
    Version: 9.1.7,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller teamcity-vstest-customlogger
   Name     = 'teamcity-vstest-customlogger'
   Ensure   = 'Present'
   Version  = '9.1.7'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'teamcity-vstest-customlogger':
  provider => 'chocolatey',
  ensure   => '9.1.7',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install teamcity-vstest-customlogger version="9.1.7" source="STEP 3 URL"

See docs at

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved by moderator ferventcoder on 10 Jul 2016.


VSTest.Console supports custom loggers, i.e. libraries that can handle events that occur when tests are being executed.
TeamCity 9.0+ has a custom logger that provides real-time test reporting.
The logger must be installed manually on the agent machine, as it requires dlls to be copied to the Extensions folder of the VSTest.Console. No agent restart is needed when the custom logger is installed.

$ErrorActionPreference = 'Stop'; # stop on all errors

$packageName= 'teamcity-vstest-customlogger'
$toolsDir   = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$url        = ''

$packageArgs = @{
  url           = $url
  silentArgs    = ""
  validExitCodes= @(0) 
  softwareName  = 'teamcity-vstest-customlogger*' 
  checksum      = '87D0B10B4430B59C9E0ABA8D61458A66'
  checksumType  = 'md5'

$programFiles = (${env:ProgramFiles(x86)}, ${env:ProgramFiles} -ne $null)[0]

$installed = $false

foreach ($version in @("14.0", "12.0", "11.0")) {
    $extensionsDirectory = "{0}\Microsoft Visual Studio {1}\Common7\IDE\CommonExtensions\Microsoft\TestWindow\Extensions" -f $programFiles, $version

    if (Test-Path $extensionsDirectory) {

        $packageArgs.unzipLocation = $extensionsDirectory
        $packageArgs.packageName = "$packageName-$version"

        Install-ChocolateyZipPackage @packageArgs
        $installed = $true

if (-not $installed) {
    Write-Warning "No compatible instances of Visual Studio were found to install the custom logger in"
$ErrorActionPreference = 'Stop'; 

$packageName= 'teamcity-vstest-customlogger' 

# Borrowed from Uninstall-ChocolateyZipPackage, but because we may be installed in multiple locations we uninstall manually

$zipContentFile=(join-path $packagelibPath '') + ".txt"
if ((Test-Path -path $zipContentFile)) {
    $zipContents=(get-content $zipContentFile)

    $programFiles = (${env:ProgramFiles(x86)}, ${env:ProgramFiles} -ne $null)[0]

    foreach ($version in @("14.0", "12.0", "11.0")) {
        $extensionsDirectory = "{0}\Microsoft Visual Studio {1}\Common7\IDE\CommonExtensions\Microsoft\TestWindow\Extensions\" -f $programFiles, $version

        if (Test-Path $extensionsDirectory) {

            foreach ($fileInZip in $zipContents) {
                if ($fileInZip -and $fileInZip -ne "") {
                    $filename = [IO.Path]::GetFileName($fileInZip)

                    $fullPath = [IO.Path]::Combine($extensionsDirectory, $filename)

                    Write-Debug "Deleting $fullPath"

                    remove-item -Path "$fullPath" -ErrorAction SilentlyContinue -Force

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status

Supports TeamCity 9.1.x

Discussion for the TeamCity VSTest Custom Logger Package

Ground Rules:

  • This discussion is only about TeamCity VSTest Custom Logger and the TeamCity VSTest Custom Logger package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or TeamCity VSTest Custom Logger, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus