Version number:
packages.config<PackageReference> tagsSpecFlow.Tools.MsBuild.Generation NuGet packageSpecFlowSingleFileGenerator custom toolEnable SpecFlowSingleFileGenerator Custom Tool option in Visual Studio extension settings<Major>.<Minor>.<Patch> Severity Code Description Project File Line Suppression State
Error MSB3030 Could not copy the file "C:\Users\******\.nuget\packages\specrun.runner\3.7.3\tools\net5.0-windows\TechTalk.SpecRun.Framework.dll" because it was not found. NoreenBackEnd.Core.Specs.Test C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.targets 4919
Error MSB3030 Could not copy the file "C:\Users\******\.nuget\packages\specrun.runner\3.7.3\tools\net5.0-windows\TechTalk.SpecFlow.Plus.RPC.dll" because it was not found. NoreenBackEnd.Core.Specs.Test C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.targets 4919
Error MSB3030 Could not copy the file "C:\Users\******\.nuget\packages\specrun.runner\3.7.3\tools\net5.0-windows\SpecFlow.Plus.Shared.dll" because it was not found. NoreenBackEnd.Core.Specs.Test C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.targets 4919
it is not working with any windows project using .net 5 and
or
create windows forms project target .net5 then create SpecFlow project using .net 5 then reference the windows forms project and try to compile
Ah, the net5.0-windows TFM is making here problems.
Ah, the net5.0-windows TFM is making here problems.
I don't understand what do you mean
In our MSBuild code, we don't check the special TFMs that came with .NET 5. The path to copy should be specrun.runner\3.7.3\tools\net5.0\TechTalk.SpecRun.Framework.dll and not specrun.runner\3.7.3\tools\net5.0-windows\TechTalk.SpecRun.Framework.dll
When it will be solved?
is there any workaround to make it work with net5.0-windows ?
We know about the issue since 2 hours, so no idea when it will be fixed. I will put it on the backlog for next iteration (starts next Tuesday).
If you want to stay with the SpecFlow+ Runner, you would need to change to the net5.0 TFM, but no idea if your application is then still working.
Alternative you can switch to another test runner like xUnit, NUnit or MSTest.
I would like to know when you will solve this issue
It is on our backlog, but we are a small team with a lot of tasks.
Until we fixed this, I would suggest using another test runner like xUnit.
Or do you need a special feature of the SpecFlow+ Runner for your project?
yes exactly we need a special feature of the SpecFlow+ Runner for our project
@muhammadyehia Which one?
the report generated after run the specs
Hey @muhammadyehia, we fixed this issue, will be in the next release.
thanks
thanks it works
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.