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

Engine extensions do not work with our dotnet tool #1505

Open
CharliePoole opened this issue Oct 21, 2024 · 2 comments
Open

Engine extensions do not work with our dotnet tool #1505

CharliePoole opened this issue Oct 21, 2024 · 2 comments
Assignees
Labels
Milestone

Comments

@CharliePoole
Copy link
Collaborator

Because the dotnet tool is a standalone executable, extensions are difficult to locate because they are installed about eight directory levels above the runner and engine. This requires a more agressive approach in searching for the extensions.

Fixing this depends on #1504

@CharliePoole
Copy link
Collaborator Author

CharliePoole commented Oct 23, 2024

@OsirisTerje @veleek This info may be helpful...

The following extensions have a .NET Standard or .NET Core target and should work...

  • NUnit V2 Result Writer
  • NUnit Project Loader (note 1)

The following extensions do not yet have a .NET Standard or .NET Core target, and therefore cannot be used at this time...

  • TeamCity Event Listener (note 2)
  • Visual Studio Project Loader (note 1)
  • NUnit V2 Driver (note 3)

NOTES:

  1. The project loaders present a peculiar issue because the projects may not contain incompatible asemblies. It's not clear what we should do if that occurs. Thoughts?
  2. TeamCity Event Listener version 1.0.9 has a .NET Standard build, but we are still using 1.0.7 because that build was only published on nuget.org and not on our other distribution points. We could test using 1.0.9 if desired. @NikolayPianikov What do you think?
  3. This will never work, since NUnit V2 tests can only run under the .NET Framework.

@CharliePoole CharliePoole self-assigned this Nov 26, 2024
@CharliePoole
Copy link
Collaborator Author

I believe this should work with the current code provided the extension is compatible - i.e. provides a .NET Standard or Core version. I'll close the issue after the following steps are done

  • Add a test showing that the V2 Result Writer works.
  • Add tests showing that each of the other extensions fails in the expected way.

Further issues should then be raised with the appropriate extension.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant