Hunting Memory Leaks and CPU Spikes with Visual Studio Diagnostic Tools
Stop guessing where your .NET performance bottlenecks are. Learn how to use Visual Studio's Diagnostic Tools to identify memory leaks via heap snapshots and CPU hot paths.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Stop guessing where your .NET performance bottlenecks are. Learn how to use Visual Studio's Diagnostic Tools to identify memory leaks via heap snapshots and CPU hot paths.
Context Since Visual Studio 2022 (17.x), the IEnumerable Visualizer opens collections in a sortable, filterable grid that loads rows incrementally, instead of forcing one-by-one expansion in the Watch window. Our team is moving debugging habits from DebuggerDisplay / DebuggerTypeProxy attributes toward this visualizer for inspecting large in-memory datasets.
Visual Studio Account‑Based Token Caching Visual Studio signs in a Microsoft or Azure AD account and caches access tokens locally. These tokens are reused for Azure resource management, Git over HTTPS, and authenticated NuGet or Azure Artifacts feeds. When a token becomes invalid—due to password change, refresh‑token revocation, or Conditional Access policy—
Goal is reliable screen reader navigation of Solution Explorer in large solutions without degrading IDE responsiveness. Visual Studio virtualizes Solution Explorer items for performance. Virtualization limits the UI Automation tree depth exposed to assistive technology, which constrains discoverability for screen reader users. Full tree exposure would improv
Goal The goal is to understand how MSBuild’s incremental build logic reacts to changes in the operating system’s time zone, and whether a normalization to UTC is necessary to prevent spurious rebuilds. Constraints & Uncertainty MSBuild compares source file last‑write timestamps against output timestamps to decide if a project is up to date. On Windows, t
I'm working in Visual Studio (2022, Enterprise edition) connected to an Azure DevOps organization and Azure subscriptions through a Microsoft Entra ID account. After my administrator adjusted my role assignments in the Azure portal, Visual Studio continued to behave as though the old permissions were still in effect for a noticeable period. My understanding
One stale cache, two documented rebuilds After an extension is installed, updated, or uninstalled, Visual Studio's MEF component-model cache can serve stale composition results: IntelliSense returns outdated completions, extension commands disappear from menus, or editor features misbehave. Microsoft's documentation offers two rebuilds, and choosing between
Context Visual Studio 2022 offers two mechanisms for applying code changes during a debug session without restarting: Hot Reload (introduced in 2022) and the legacy Edit and Continue (EnC). Hot Reload applies edits while the process continues running, supporting a wider range of changes such as adding methods, modifying lambdas, and updating Razor components
Visual Studio launches IIS Express or Kestrel for local web projects, and the browser typically displays localhost. The underlying socket may listen on 0.0.0.0, making the debugging endpoint reachable from any device on the same LAN. Verification requires inspecting the site binding in the .vs folder’s applicationHost.config and confirming the listening addr