Youssef Victor
Youssef Victor
I haven't went through all comments, but the general main issue I'm seeing is the ability to run Stryker VSTest extension in the same process that runs the tests. This...
> MTP can optionally be used for dotnet test. This depends on whether the user has defined TestingPlatformDotnetTestSupport to be true in the project PropertyGroup. By default, it uses VSTest....
It's relying on implementation details, but you can have a target that runs before `UnoImplicitPackages` and remove Uno.Resizetizer from `_UnoProjectSystemPackageReference`. But I'm not sure if everything will work fine without...
Moving to uno.extensions as this is where the generator in question is implemented
I haven't played with the repro but I think TUnit users will have to add the Polyfill package reference themselves and enable the use of embedded attribute. Alternatively, if TUnit...
This is green already, but one needed enhancement first is to avoid using `DependencyPropertyDetails` for IsPropMethodCall DPs as the value is already stored in the DependencyObject itself. We need to...
In 17.14, the testhost is net8.0, while it was netcoreapp3.1 previously. And the behavior difference is coming from there. We are running testhost.x86.exe with `DOTNET_ROOT` pointing out to `C:/Program Files/dotnet`....
Using 17.13 (where testhost.x86.exe is netcoreapp3.1), I see ``` Using global installation location [C:\Program Files (x86)\dotnet\] as runtime location. ``` Using 17.14 (where testhost.x86.exe is .NET 8), I see ```...
It looks like the logic will prefer DOTNET_ROOT_X86 but still falls back to `DOTNET_ROOT` https://github.com/dotnet/runtime/blob/f77f791953e7e8af4bd1ce33981a9059f4c9f207/src/native/corehost/hostmisc/utils.cpp#L373-L376