Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Load an extension from sources' paths #616

Closed
NikolayPianikov opened this issue Mar 15, 2017 · 2 comments
Closed

Load an extension from sources' paths #616

NikolayPianikov opened this issue Mar 15, 2017 · 2 comments

Comments

@NikolayPianikov
Copy link

NikolayPianikov commented Mar 15, 2017

Description

It will be good to try finding and to load extensions from the directories specified in sources' paths - to have ability to add my extension as reference to a NuGet package for a test project.

Steps to reproduce

dotnet test -l=teamcity
for netcoreapp1.0 test projects

See this solution to reproduce.

Expected behavior

For example when I run tests using my custom logger dotnet test -l=teamcity it works for net45. And it is good.

Actual behavior

But when I run similar tests using my custom logger for netcoreapp1.0. it does not work.

And I should run tests as dotnet test -l=teamcity -a=. Only in this case the extension for my logger is loaded as I wish.

Environment

VS 2017
Microsoft.NET.Test.Sdk version="15.0.0"
Windows 10

@codito
Copy link
Contributor

codito commented Mar 15, 2017

@NikolayPianikov this is recently fixed in master (#557). Will update when a package is available to play with.

@NikolayPianikov
Copy link
Author

@codito thank you

@pvlakshm pvlakshm mentioned this issue Apr 4, 2017
17 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants