As I was troubleshooting my issues with Elastic logger configuration, I couldn't get the debugging in Visual Studio 2022 to work for the Elastic.Extensions.Logging NuGet package, although it appeared to have SourceLink correctly set up, and I could navigate its source code without any issues. When I tried it in JetBrains Rider, it just worked. I decided to get to the bottom of this.
I spend a significant part of my work day in a terminal. That's why I have it configured to suit my needs with a collection of several useful modules which I occasionally still extend. Although all IDEs I regularly use feature an integrated terminal which opens in repository root by default, I rarely used them because they didn't match my configuration. So I decided to check if there was a way to make them use my default PowerShell profile.
By default, JetBrains Rider displays additional type information and parameter names in text editor windows. They are called inlay hints. Visual Studio's default configuration doesn't display any such type or parameter information. You only see what is already present in the code.