obligaron

> Of course this is a special situation, because normally no one is using the -local version of the packages, but it is painful still. Sorry for the misunderstanding. I...

Btw: If we revive #64 (which was reversed because of #152), we could avoid the locks in visual studio. Maybe we could make #64 conditional for windows only?

If we want to ensure that the deletion works, we would probably need something like you suggested ((check old renamed folder exists and delete if present) -> rename -> delete)....

I missed that I could check that the rename directory exists in `Condition`. 😉 So I tried to implement this, but I failed because the `Move` Task [doesn't support](https://github.com/dotnet/msbuild/issues/8795) moving/renaming...

I updated/ignored the tests. I keep the PR as draft until we start with developing v3.0.

Could you add a `TUnitGenerationTest' under `SystemTests\Generation' (see `MsTestGenerationTest' for an example). This will ensure that the basic functionality of Reqnroll is tested with TUnit in our CI/CD pipeline (we...

I fixed the compilation error. Background is: ```xml ``` I also added trx support for TUnit for our test infrastructure. But we need the test output in the trx files....

I investigated why the `Before_After_Feature_hooks_execute_only_once_on_sequential_run_even_with_failing_feature_hooks` test fails. This test disables parallel execution and checks whether a BeforeFeature/AfterFeature is executed only once per feature. Background: To reduce overhead and allow users...

> Do we have any idea when this might be ready for release? We have recently started using TUnit for integration/functional tests and I would love to start using ReqnRoll...

The test `Scenario_outline_examples_gather_tags_and_parameters` fails, because TUnit implicitly converts one (null) parameter to an array with one null value. See the following TUnit example (without Reqnroll): ```csharp [Test] [Arguments("sample", null)] public...