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

Add support for VS projects and solutions #227

Closed
CharliePoole opened this issue Sep 17, 2014 · 2 comments · Fixed by #429
Closed

Add support for VS projects and solutions #227

CharliePoole opened this issue Sep 17, 2014 · 2 comments · Fixed by #429

Comments

@CharliePoole
Copy link
Contributor

This is a feature already included in NUnit 2.6 and at least partially implemented in the engine already.

  • Running a VS Project should work the same as running the output assembly from the project. If a project type is not one we support, an error message should result.
  • Running a Solution should be equivalent to entering the names of all the output assemblies on the command line. Any project types we don't support can be skipped without notice. Filtering for test assemblies supported by NUnit 3 is an option if it can be done easily using the engine.
  • This issue in the old nunit-console project can be dealt with at the same time as this one by ignoring any projects that are disabled in the configuration: Make everything build after big split nunit-console#1
@rprouse
Copy link
Member

rprouse commented Oct 29, 2014

When we do this, make sure that we support F# projects. An issue was entered reporting that they do not work in 2.6.3.

nunit/nunit-console#43

@CharliePoole
Copy link
Contributor Author

Another note: We should decide what to do about project types we don't recognize. There are pitfalls either way we go.

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

Successfully merging a pull request may close this issue.

2 participants