vstest: Unable to specify path to a custom logger on 'dotnet test' command line

There is no way to specify a full path to a custom logger on command line. Loggers are only discovered from sdk\{version}\Extensions directory. This makes it cumbersome to use a custom logger from a nuget package.

Proposal:

When the logger name passed to --logger is a path to an existing .dll use that. Otherwise look it up by name in the Extension directory.

--logger:"C:\users\user\.nuget\packages\mylogger\lib\mylogger.dll";parameters

About this issue

Original URL
State: closed
Created 7 years ago
Reactions: 3
Comments: 17 (16 by maintainers)

Most upvoted comments

OMG I’ll add this info here, in case someone in on a verge of nervous breakdown and is looking for this info like me:)

if you have a custom logger and you want to use friendlyName, or url to specify logger you want to use, you have to put your logger in assembly that ends with .TestLogger.dll for example my.TestLogger.dll without it you have to use I think setting file and specify CodeBase and AssemblyQualifiedName to load your logger.

maciejw on Oct 16, 2020

would be better if test platform could use the logger already implemented in xunit

+1. Xunit already has loggers for TeamCity, AppVeyor, HTML, and others. Would be nice we could use them from dotnet-test. cref https://github.com/Microsoft/vstest/issues/254.

natemcmaster on Feb 27, 2017