OpenTelemetry Plugin for JetBrains Rider: Observability Inside Your IDE | by Sasha Ivanova.

https://blog.jetbrains.com/dotnet/2025/06/16/opentelemetry-plugin-for-jetbrains-rider/

#opentelemetry #visualstudio #rider #observability #dotnet #csharp

Dew Drop – June 17, 2025 (#4441)

https://www.alvinashcraft.com/2025/06/17/dew-drop-june-17-2025-4441/

#dotnet #ai #visualstudio #webdev #cloud #windowsdev #mobiledev #csharp #devops #dewdrop

Sigh, Visual Studio Installer has the feature to "rollback" to a previous version with just one click. But only for one step back. (For me, it was from 17.14.5 to 17.14.2.) When you have done that, it doesn't offer any further rollbacks. Irritating. #VisualStudio

Edit: But oh well, I figured out another way to work around my problem.

So, I am a little confused how I'm supposed to find the compiled-for architecture in CMake on Windows with MSVC or the corresponding llvm/clang-cl distro, to detect e.g. ARM64 builds...

In theory, CMAKE_HOST_SYSTEM_PROCESSOR should stay at AMD64 (or whatever) while CMAKE_SYSTEM_PROCESSOR (the target/build platform, not the build host platform) should say something like ARM, right? That's how it works for manually-set-up cross compiling...

But, unless you manually change that (!), when you set up a build for ARM for the MSVC toolchain on the command line, or from Visual Studio, or with Visual Studio's built-in presets for ARM support thru CMake (via Open Folder), the only thing that tells you the real architecture is CMAKE_C_COMPILER_ARCHITECTURE_ID and friends. Which is ostensibly "internal".

Pretty frustrating. Feels wrong to use a supposedly-internal variable, but at least that one's documented, unlike the other mention of ARM in the CMakeCache.txt.

#CMake #VisualStudio #MSVC

Use Copilot Agent Mode in Visual Studio (Preview)

https://learn.microsoft.com/en-us/visualstudio/ide/copilot-agent-mode?view=vs-2022

#HackerNews #CopilotAgentMode #VisualStudio #Preview #TechNews #AIinDevelopment