There are several pitfalls if you are using wfastcgi, most notably, the FastCGI scriptProcessor name generated by wfastcgi-enable is incorrect if your Python executable path contains whitespace (e.g., “Program Files”).
This is a known issue that pwsh will hang after executing any external command if $TERM is screen, i.e. you are running pwsh inside a screen. However, according to the GitHub comment, it seems screen is to blame.
All you need to do is to copy llvm.natvis and clang.natvis and paste them into your documents\Visual Studio 201x\Visualizers\ folder. Then you can see the content of DenseMap and Decl really easy in Visual Studio debugger.
I’ve noticed that MS announced their first pre-release for Workbooks, which allows you to experiment with .NET Framework / .NET Core / Xamarin / WPF in a Jupyter-like fashion. It’s like an enhanced version of C# interactive window.
What is really an improvement, is that you can add reference to NuGet packages in a similar way as you are working with a full C# project, so it exhibit a chance for me to play with WikiClientLibrary. Hopefully, it might give Wiki contributors some convenience on automated edits, such as word-replacement in batch.
Content is available under CC BY-SA 3.0 unless otherwise noted.