-
Notifications
You must be signed in to change notification settings - Fork 2
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
Look for DLLs in RID directory, not just EXEs #37
Comments
That's strange! Is there a |
My folder structure is Debug\net46\win7-x64. That folder contains both dotnet-test-nunit.exe and nunit.framework.dll. |
Could you check that |
Yes, it is. |
Can I see your |
Yes, it is here. You can run the Specify.Tests project. In particular it is the APIs\SemanticVersioningTests.cs. I don't know if the #if directives are somehow influential. |
Got it, thanks! It looks like I'm making the incorrect assumption that apps that target "netcoreapp1.0" must have an entry point / be EXE files when compiled for .NET. It appears they don't actually have to be a console application (this just happens to be the way they're set up in the .NET Core project templates). Hopefully this is simply a question of how I search for the .NET Framework assembly. I need to find the one in |
Have to admit, I'm quite hazy on the difference between console projects and class library ones. For example, if I created a class library, and then realised it should be a console app, can I edit the xproj or something? (apart from adding a main method, etc.). I don't think there is an option in the VS tooling in project properties. |
Could you give this build a try: |
Seems to be working. 😄 |
Yup, sure does. Love your work @jcansdale ! |
My xproj test project targets netcoreapp1.0 and net46 (project.json defines them in that order). I have some tests that use a dependency that is only net46 so I am using #if directives to make it compile:
When I right click the file and choose Test with > .Net Framework, I get the following error:
The text was updated successfully, but these errors were encountered: