Building a Reqnroll project with NUnit on macOS ARM64 architecture

[bgoggan]

Has anyone successfully build their projects using Reqnroll.Nunit on an ARM64 based architecture? We just recently migrated from Specflow and everything works fine on our testers with windows machines but we have 1 with a Mac based on the above architecture and we receive the below error when building. Any thoughts??

Reqnroll.NUnit.targets(34,5): Error MSB4216 : Could not run the "ReplaceTokenInFileTask" task because MSBuild could not create or connect to a task host with runtime "CLR4" and architecture "x64". Please ensure that (1) the requested runtime and/or architecture are available on the machine, and (2) that the required executable "/opt/homebrew/Cellar/dotnet@6/6.0.125/libexec/sdk/6.0.125/MSBuild.exe" exists and can be run.

Mac of course doesn't support the .exe extension so I'm not sure how to move forward, if we can.

[gasparnagy]

@bgoggan Just that I understand fully... Why the tester with the Mac would need to build Reqnroll itself? Are they would like to contribute to the project?

(Our build runs on Linux and it works there, so the platform itself should not be an issue in general.)

[bgoggan]

@gasparnagy We are now able to build the projects but the .feature files are not created, so all we had was the .feature.cs files.....We're going to completely uninstall his version of Rider and start fresh just in case something was wrong. We'll start again with the QuickStart project and see what happens. I'll keep you posted.

[ajeckmans]

The feature files are there. It is a bug in the rider plugin which hides the feature files (or well, excludes them from the project visually). You can use the workaround posted here: reqnroll/Reqnroll.Rider#1

[bgoggan]

@ajeckmans So, the workaround is to add the new itemgroup with the value? We tried that but still the features do not appear in the solution.

[bgoggan]

@ajeckmans Sorry, standby. It worked on the QuickStart project so we're looking more closely at our project.

[bgoggan]

@ajeckmans Ok, we had to update our workaround to the below since we nest our features in sub-directories but it does work.
<ItemGroup> <Content Include="Features\**\*.feature"/> </ItemGroup>