IT-VBFK

Another workaround I discovered is: ```csharp Tool cmake = ToolResolver.GetPathTool("cmake"); CMake($"-G {"Visual Studio 16 2019".DoubleQuote()}"); ``` But this also seems to be a hack...

> In general, the Docker team needs to clearly document macOS versions and associated Docker Desktop versions. Docker Desktop 4.25.0, a minor version, should work with macOS 11.7.10 (Big Sur)....

Can I throw in another thought, or is it too late? In https://github.com/fluentassertions/fluentassertions/pull/2321 we changed the behavior to _not_ check two things in one method. So, why now? (e.g. `HaveElementWithValue...

Rebase to current develop and force push

Have you noticed the compile error in last pipeline run? https://github.com/fluentassertions/fluentassertions/actions/runs/9318831327/job/25663184462

What about this (to avoid this indexers): ```csharp [Test] public void SomethingReturnsValidCode() { var resultOfSystemUnderTest = "abc123XY"; resultOfSystemUnderTest.Should().MatchRegex(new Regex(@"(abc?)(\d{3})([X-Z]*)")) .Which.Groups.Should().SatisfyRespectively(group0 => {}, groupX => { groupX.Should().Be("123") }, ...); } ```...

Ou.. I was not aware that this should be the PR for #2589 when I opened #2690 @skukshaus You most definitely can cherry-pick everything from #2690 to finish this if...

```csharp poco.Should().BeEquivalentTo(proto, static options => options .WithAutoConversion(g => g.ToString(), s => Guid.Parse(s))); ``` Why do we need two conversion lambdas here? I think the generic parameters already tells, what converts...

@eranikid Rebase onto current develop and force push should fix the pipeline..