September 2020 (version 1.50)
Join VS Code at Microsoft Ignite or catch the sessions online. A year of VS Code, wrapped. Explore the highlights. September 2020 (version 1.50) Update 1.50.1 : The update addresses these issues . Downloads for 1.50.1 Windows x64 Arm64 macOS Intel Linux .deb .rpm .tar.gz Arm instructions Snap Welcome to the September 2020 release of Visual Studio Code. There are a number of updates in this version that we hope you will like, some of the key highlights include: Accessible settings editor - Interact with the settings list like any other list in VS Code.
Pinned tabs improvements - Resize pinned tabs, unpin with one click, and more. Linux ARM builds - VS Code is now available for both Linux ARMv7 and ARM64. Improved debugging experience - Improved hover and filtering in debug console. New JS debugger features - Toggle auto attach flows and see performance in real-time. Panel layout improvements - New panel maximization settings and bottom panel size. Webview Views support - Build extensions with webview views in the sidebar and panel.
Updated "Create a Dev Container" tutorial - Get started with Development Containers. If you'd like to read these release notes online, go to Updates on code.visualstudio.com . Join us live at the VS Code team's livestream on Tuesday, October 13 at 8am Pacific (4pm London), to see a demo of what's new in this release and ask us questions live. Insiders: Want to try new features as soon as possible? You can download the nightly Insiders build and try the latest updates as soon as they are available. macOS: Keychain access moved to a different process Some changes in this release around how the macOS Keychain is accessed from VS Code will require you to acknowledge the following prompt for keychain access on macOS, even if you've previously allowed keychain access: Details: VS Code previously accessed the macOS keychain from the window process itself, but now accesses it from the main process.
As such, for macOS it prompts for approval like a new application is requesting access, because the process is a different one from before. Accessibility Settings editor Back in July, we mentioned in the 1.48 release notes that we were investigating ways to improve the accessibility of the settings editor. After a few months of talking to screen reader users, experimenting, prototyping, and gathering feedback from the community, we are shipping the new experience, which we believe is an improvement for all keyboard-heavy users, whether using a screen reader or not.
In this new interaction model, interacting with the settings list works more like interacting with any other list in VS Code. With focus in the search bar, you can press the down arrow to focus a setting row. Then you can use the arrow keys to move focus around the settings list. To edit a setting, you can press enter to set focus on the control in the setting row. If you would like to read more about the motivation and thinking behind this approach, please see GitHub issue #108006 .
Workbench Pinned tabs improvements Pinned tabs were introduced in our May 2020 release. Since then, we've received valuable feedback on how to improve this experience further, and for this milestone there are a couple of changes worth mentioning. A new setting workbench.editor.pinnedTabSizing allows you to configure how large a pinned tab should appear: normal : a pinned tab inherits the look of other tabs (new default) shrink : a pinned tab shrinks to a fixed size showing parts of the editor label compact : a pinned tab will only show as icon or first letter of the editor label If you liked how pinned tabs looked prior to this release, make sure to configure "workbench.editor.pinnedTabSizing": "compact" .
Pinned tabs also show a new "pinned" icon to allow you to unpin with one click. This icon will also appear in the "Open Editors" view. Theme: GitHub Light Some other improvements include: Editors can now be pinned even when tabs are disabled. Cmd+W ( Ctrl+W ) no longer closes a pinned editor, but selects the next non-pinned editor. A new command workbench.action.closeActivePinnedEditor can be assigned to close a pinned editor.
A new tab.lastPinnedBorder color can be assigned to draw a border to the right of the last pinned tab. Renamed some editor-related context keys A few new editor context keys have been introduced, deprecating some of the existing ones. If you are using these in your keybinding settings, please update them: groupActiveEditorDirty was renamed to activeEditorIsDirty editorPinned was renamed to activeEditorIsNotPreview editorSticky was renamed to activeEditorIsPinned Added new resource (explorer-related) context keys Two new context keys have been added for resources. resourceDirname for the folder path of the resource, equivalent to dirname(uri.fsPath) resourcePath for the full path of the resource, equivalent to uri.fsPath Extensions: Simplified recommendation notifications In this release, we improved the experience of recommending extensions using notifications by making them smarter and less noisy to users.
Recommendations notifications are not shown again after you tried them or went through them. Only one recommendation notification is shown at any time in VS Code window. You can access already recommended notifications under the notification manager, the bell icon in the status bar. Theme: GitHub Sharp Dark Recommendation notifications supporting installations, like WSL, Docker etc., on your system, are made less noisy by showing only one such notification once per VS Code session - a session begins when you open VS Code and ends when you quit.
Panel layout improvements New panel maximization setting For those who prefer to work with the panel maximized, you no longer have to maximize the panel each time after toggling it open. For those that don't, the old panel behavior isn't going away. Instead, a new setting, panel.opensMaximized , allows users to adjust to their own preference whether or not the panel always opens maximized when toggled with Toggle Panel .
The options are always , never , and the default value preserve . The preserve option opens the panel maximized if it was maximized before being closed, and opens it non-maximized otherwise. Additionally, if the panel is hidden, Toggle Maximized Panel will now always open the panel maximized. Decreased minimum window width when panel is on the bottom When the panel is on the bottom rather than on the side, the minimum window width is 400px instead of 600px.
This way, developers who want a narrower editor-only or panel-only window can now move the panel to the bottom, optionally hide or maximize it, and then resize the window to the new narrower minimum width. Linux ARM builds VS Code is now available for both Linux ARMv7 and ARM64 architectures. This means you can now officially use VS Code on a Raspberry Pi, Chromebook, and other ARM-based devices! On these devices, you can also leverage the VS Code extensions for Remote Development to get access to more powerful development environments when you need them.
Download it now ! Also available for Insiders . Editor Trigger IntelliSense For years, Ctrl+Space has been the predominant keybinding to trigger IntelliSense. However, on macOS and Windows, the same keybinding is used to toggle between keyboard layouts. To minimize confusion, we added another keybinding to trigger IntelliSense: on Windows and Linux it's Ctrl+I , and on macOS it's Cmd+I . Debugging Debug hover improvements Language hover now available while debugging While debugging, the debug hover takes precedence over the language hover, making it impossible to see the language hover.
Starting with this release, you can switch from the debug hover back to the language hover by holding down the Alt modifier key. As long as Alt is pressed, the language hover is shown instead of the debug hover. This makes it much easier to read Javadoc while debugging. Auto sizing debug hover In order to minimize the need f
The rest of this page is on the live site.