A young boy dressed in paper boy hat and retro attire stands on a stool calling out his message through a megaphone. He is on a rural road in the mountains of Utah County, Utah, USA.
The November 2018 release of Visual Studio code (version 1.30) is now available. This version has multiline search improvements, custom tile bars for Linux, a simplified debug configuration and other changes.
We take a look at the major updates in the November 2018 of Visual studio code.
In the October release, support for multiline search was added. Now, the search UX has been improved for easier usage. Users can search with multiline text without writing a regular expression. Press Shift+Enter in the search box to insert a newline. The search box will grow to show the full multiline query. Users can also copy paste multiple lines from the editor into the search box.
The accessibility and themability of menus has been improving over the past releases on Windows through the custom title and menu bar. This was optionally available on Linux, it will now be enabled by default. You can use the native title bar by setting the window.titleBarStyle to native.
The References view has moved out of preview and is now available generally. There are two commands:
Hidden on startup, the References view will remain visible once it has been used. When all search results are cleared, a history of previous searches is shown.
New snippet variables are available that insert line or block comments to honor the current language. BLOCK_COMMENT_START and BLOCK_COMMENT_END for using block comments and LINE_COMMENT for lines.
Any JavaScript and TypeScript anonymous callbacks were previously labeled as <function>. This was in the Outline view, breadcrumbs view, and document symbol list. Due to this, it was impossible to tell which function a developer was really after. TypeScript 3.2+ allows VS Code to display more context for callback functions, so now they can be differentiated from one another.
Fenced code blocks and other Markdown elements within JSDoc blocks are now syntax-highlighted.
In this release, an area of improvement was to simplify the generated launch.json file for the most popular debug extensions. The goal was to encourage users to start and configure debugging. Unnecessary launch configuration attributes were hidden. Using the Quick Pick UI for better user interaction while generating the initial launch.json was also a part of this.
A task that users always run on opening a folder can now be configured to run automatically. This can be done by configuring its “runOn” property when that folder is opened. This was done to make sure no one breaks the new strict null checks in the VS Code repository. On adding “runOn”: “folderOpen”, everyone who allows tasks to be run automatically will get markers the strict null check is violated.
A previous version of an extension can be used if the current version has problems. An Install Another Version action is provided on an installed extension, on clicking it, a dropdown of available versions is shown.
HTML custom tags / attributes support is added which allows developers to specify a list of tags and attributes that VS Code loads during startup.
Network proxy support for extensions for enabling network proxy support for all extensions by using Http: Proxy Support.
Code completion suggestions via IntelliCode comes to C++ in Visual Studio 2019
Neuron: An all-inclusive data science extension for Visual Studio
I remember deciding to pursue my first IT certification, the CompTIA A+. I had signed…
Key takeaways The transformer architecture has proved to be revolutionary in outperforming the classical RNN…
Once we learn how to deploy an Ubuntu server, how to manage users, and how…
Key-takeaways: Clean code isn’t just a nice thing to have or a luxury in software projects; it's a necessity. If we…
While developing a web application, or setting dynamic pages and meta tags we need to deal with…
Software architecture is one of the most discussed topics in the software industry today, and…