ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #vscode
Learn how to diagnose and resolve 'Extension Host Terminated Unexpectedly' errors in VS Code using Process Explorer, Extension Bisect, and host logs.
Update Mechanism and Data Persistence Visual Studio Code employs a background update process that separates the application binaries from user-specific configuration and extensions. When an automatic update fails, the system typically reverts to the previous stable binary version to maintain application availability. Recovery Constraints While the internal u
The goal is to run VSCode integration tests without exposing production credentials, using a documented method for secret handling. Constraints include limited support for the Secret Storage API in VSCode versions prior to 1.70, potential visibility of environment variables to other processes, and the lack of automatic secret clearing in the test harness, wh
When managing Visual Studio Code in environments with strict outbound network traffic limits, reducing the frequency of HTTP requests to telemetry endpoints is a priority. The telemetry.enableTelemetry setting provides a mechanism to control the transmission of usage data and crash reports to Microsoft servers. Choosing to disable telemetry entirely eliminat
Goal Determine the idle timeout that causes the VS Code Remote - Tunnels server to shut down when a tunnel is inactive, so that low‑traffic development workloads can rely on predictable server availability without incurring unnecessary compute costs. Uncertainty The extension’s documentation does not specify the timeout value, and no user‑exposed setting exi
The goal is to minimize VS Code’s notification interruptions while still surfacing alerts that require immediate attention. The available controls include a global toast toggle, per‑extension silencing lists, and the option to hide the Notification Center badge, but each approach either suppresses all toast notifications or requires manual maintenance of ext
Extension Host Recovery Behavior Visual Studio Code utilizes a separate process for the Extension Host to ensure UI stability. When this process terminates unexpectedly, the editor triggers an automatic restart mechanism to restore extension functionality and displays the notification "Extension Host crashed". While the memento API allows extensions to persi
The goal is to have a custom file extension, such as *.foo, recognized as JavaScript both when editing files locally in VS Code and when the same workspace is opened through the Remote‑SSH extension on a production Linux host. Locally, adding "*.foo": "javascript" to the files.associations setting activates the correct language mode, but when connecting via
VS Code Update Manager Visual Studio Code employs a background update mechanism that downloads packages to a separate directory before swapping the active installation. While the system is designed to maintain the previous stable version if a download fails, a partial update failure during the swap process can lead to an inconsistent binary state. When a man