Wills Ward

Sure. We have a project that sets `` in `Directory.Build.props`, per this issue. Version 4.2.0 would fail to build the project when simply running `dotnet stryker`, but we were able...

We do define a `TargetFramework`. We do it in this manner: *Directory.Build.props* ```xml net8.0 ``` *.csproj* ```xml $(ProjectTarget) ``` I cannot provide any access to the proj files, unfortunately, but...

@rouke-broersma Not all of our project are able to target the same framework. Analyzer projects, for example, must target netstandard2.0 for VS compatibility. Nonetheless, I will attempt to get a...

@dupdob I have a minimal repo that I can share. [Repro.zip](https://github.com/user-attachments/files/20783790/Repro.zip) Out of the box, the following fails: ```bash > dotnet stryker -tp .\Tests\Tests.csproj -p Library\Library.csproj _____ _ _ _...

Ok. I ran with `--dev-mode` with the non-working configuration, and this was the result: ```text [08:00:14 WRN] Project analysis failed. The MsBuild log is below. [08:00:14 INF] Started process 33728:...

If the MSBuild version selection isn't part of Stryker, then I completely agree. Seems like this is a "me" problem :D. At least this has been documented, and could assist...