Closed 304NotModified closed 4 years ago
It's a problem with SpecFlow (XUnitAssemblyFixture
), which I solved in #18 for CI/CD but it still occurs in VS2019 occasionally (only if you try to build the project, not if you're using the NuGet package). Background info at https://github.com/SpecFlowOSS/SpecFlow/issues/1825; their suggestion of disabling Full Solution Analysis in VS 2019 does work, but it's not the solution I'm looking for..
BTW, you can run the tests from the command line using dotnet
:
dotnet test --configuration Release --framework netcoreapp2.1 SpecFlow.DependencyInjection.Tests
dotnet test --configuration Release --framework netcoreapp3.1 SpecFlow.DependencyInjection.Tests
Again, this is a workaround.
Thanks! I think also it's https://github.com/SpecFlowOSS/SpecFlow/issues/1825 :)
Hi,
I have a question,
For some reason I have build errors locally (tested on 2 machines), when both targetframeworks are enabled.
This works:
This also:
And this gives a lot of strange build errors:
Any idea what's wrong? It's working with you guys?
I'm using Visual Studio 2019 16.4.5 (also the same issue was on 16.4.4, just updated and retested it)