Konstantin Preißer

Hi, just some random thoughts; I don't know if this will help or whether you are already aware of this: When using the `Span` types in .NET Core and in...

I took a closer look on the call stack and the relevant code when the crash happens, and I think the situation described in my previous post can actually be...

I can reproduce this problem on Windows with .NET Core SDK 3.1.201 when using a [**case-sensitive**](https://devblogs.microsoft.com/commandline/per-directory-case-sensitivity-and-wsl/) directory: 1. Create a new directory and make it case-sensitive (requires Windows 10 Version...

> That page also says the API is available in .NET Standard 2.0, which is supported by .NET 4.6.1. Note that the first version of .NET Framework that fully supports...

Note that using `arm64` for C++/CLI projects targeting .NET Framework seems to require VS 2022 17.3 and using the `v143` toolset, as that includes an ARM64 version of `mscoree.lib`. However,...

Hi, > AnyCPU apps can be run as ARM64 (or any other architecture, excluding ARM32 since .NET Framework ARM32 is not available) with start /machine your-app.exe in Windows 11 22H2....

I think this might also be a nice gimmick for a (modal) Task Dialog, e.g. when using progress bars:  Or when using the colored icon bars: 

Hi @paulbartrum, I can reproduce the StackOverflowException and the long run time just by creating a new ScriptEngine and executing the code from @rodrigoroma without the self-executing function expression, using...

Hi @paulbartrum, I rebased the PR on the current `master` branch. Additionally, I removed the usage of `DateTime.MinValue` to represent an invalid date, because this can lead to problems when...

> I'm pretty sure even if you make StackFrame a struct, it'll get boxed as soon as you push it on the `stackFrames` stack. Actually, as `stackFrames` uses the generic...