Youssef Victor

Ah okay. I misinterpreted that. In that case, yes there could have been slight change in behavior. I need to double check that. I assume you are not enabling test...

@seanhalliday Can you please upload a complete repro project? Also did you try MSTest v4 preview?

As other test frameworks have proper assembly versioning, if this ever caused issues, I won't consider it an MSTest issue.

Moving to MSTest for now. I'll investigate.

This is likely already fixed (same fix/issue as https://github.com/microsoft/testfx/issues/3018). So I'm going to close this.

@copilot There is a merge conflict. Can you fix it?

@nohwnd Yup, they are the mocked tests. The PR you referenced touched the ones I was referring to (and more). It would be nice to fix these up.

To detect the invariant mode, here are the relevant parts from .NET runtime: ```csharp GetBooleanConfig("System.Globalization.Invariant", "DOTNET_SYSTEM_GLOBALIZATION_INVARIANT"); internal static bool GetBooleanConfig(string switchName, bool defaultValue) => AppContext.TryGetSwitch(switchName, out bool value) ? value...

This is by-design. `--timeout` only requests cancellation. Can you try HangDump extension for MTP instead of `--timeout`? See https://learn.microsoft.com/dotnet/core/testing/microsoft-testing-platform-extensions-diagnostics#hang-dump for information. But in short, add Microsoft.Testing.Extensions.HangDump to your test projects,...

`--timeout` is not intended to be a "hard kill" or produce a dump. If you really need a dump, you need to use `--hangdump` provided via Microsoft.Testing.Extensions.HangDump. Keep in mind...