Visual Studio Code July 2019

Update 1.37.1: The update addresses these issues.

Downloads: Windows: User System | Mac | Linux: snap deb rpm tarball

---

Welcome to the July 2019 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:

• Full product icon refresh - New modern icons across all of VS Code.
• Edit string arrays in the Settings UI - Add to string arrays directly from the Settings editor.
• Reveal search result in File Explorer - Quickly jump to file locations in the File Explorer.
• Show whitespace in selection - See whitespace characters just for selected text.
• Find and Replace preserves casing - Replace text without losing letter casing.
• Terminal search UX improvements - More intuitive bottom-up search order for the terminal.
• Better SCSS @import navigation - VS Code now checks more locations for SCSS files.
• Remote Development tutorials - New tutorials for working over SSH and in WSL.

If you’d like to read these release notes online, go to Updates on code.visualstudio.com.

You can also check out this 1.37 release highlights video from Developer Advocate Brian Clark.

Insiders: Want to see new features as soon as possible? You can download the nightly Insiders build and try the latest updates as soon as they are available. And for the latest Visual Studio Code news, updates, and content, follow us on Twitter @code!

Workbench

New product icons

We’ve updated all of our product icons to be uniform in style, color, and size. We went through various iterations and the community was helpful in providing feedback through every step of the process.

Note: This does not cover our use of Octicons, those icons appear in the Status bar and Quick pick.

Settings editor support for string arrays

The Settings editor now allows editing array-of-string settings. The Add Item button will bring up an input box to add a new string.

Extension authors can enable this support by contributing a configuration with type and items keys:

{
  "type": "array",
  "items": {
    "type": "string"
  }
}

Removed warnings from settings files

You will no longer see warnings for unknown or unsupported settings in your settings.json files. Instead inactive settings will be faded, similar to unused source code, with a hover explaining why. In addition, you won’t see warnings for settings from extensions that are currently disabled.

Reveal search result in the Explorer

The file context menu in the Search view now has a Reveal in Explorer command to navigate to that file in the File Explorer.

Search regex features

Back in the 1.29 release, we added the setting search.usePCRE2 to make search use the PCRE2 regex engine. This enabled searching with some advanced regex features such as backreferences and lookahead assertions. Thanks to some upstream work in ripgrep, you can now use these features without enabling a special setting. ripgrep will fall back to the PCRE2 engine automatically if the regex uses a feature that isn’t supported by the Rust regex engine, and search.usePCRE2 is now deprecated. As a reminder, VS Code only supports regexes that are valid in JavaScript, because open editors are still searched using the editor’s JavaScript-based search.

NPM Scripts Explorer visible by default

Previously, you had to enable the setting npm.enableScriptExplorer to make the NPM Scripts Explorer visible and this was difficult to discover. The NPM Scripts Explorer is now shown collapsed in the File Explorer, when there is a package.json file at the root of the workspace.

When you have no package.json at the root in your workspace, you can still use the setting to enable the NPM Scripts Explorer. If you want to hide the explorer, you can right-click on its title and select Hide from the context menu.

focusedView context key

There is a new keybinding when clause context key, focusedView, to display or enable a command when a given view is focused.

"when": "focusedView == nodeDependencies"

Accessibility improvements

We fixed accessibility issues across the workbench. A full list of the issues fixed can be found on GitHub with the ‘accessibility’ label.

New tree widget adopted in tree view

Extensions that contribute tree views will now get the new tree widget experience. The tree widget provides better performance as well as improved keyboard navigation, filtering, custom indenting, horizontal scrolling, and more. If your favorite extensions have custom tree views, you should see the same UX improvements that were added earlier to the built-in VS Code explorers.

Editor

Show whitespace in selection

The editor.renderWhitespace setting now supports a selection option. With this option set, whitespace characters will be shown only on selected text:

This is handy for quickly checking whitespace without filling the entire editor.

Improved minimap search results visibility

In the previous release, we introduced search decorations in the minimap (code outline). These decorations were difficult to see, so this iteration, we’ve worked on increasing their visibility. Now, the entire line will now be highlighted with low opacity in the minimap, and the actual match shown with high opacity.

You can also change the color of the decorations using the new minimap.findMatchHighlight theme color.

Preserve case in Find and Replace

You can now preserve case when doing replacement in the editor’s Find widget. The feature is turned on when the Preserve Case option (AB button) is turned on in the editor’s Replace input box.

Currently VS Code only supports preserve Full Upper Case, Full Lower Case, and Title Case.

Button toggle active state in Find widget

We’ve updated the Find widget’s button toggle active state with a filled background so that you can now easily tell when you are focused on an active toggle. This appears in the Search view, Find and Replace, and Terminal Find.

With this update, we’ve introduced a new theme color, inputOption.activeBackground, to control the background color of the toggle active state. This color reuses focusBorder so that it works better with themes by default. We’ve also set the default for inputOption.activeBorder to transparent so that the border is only used for focus.

Updated info colors

Following the unification of the warning colors, we’ve also updated editorInfoForeground and editorInfoBorder to match the rest of the information diagnostics colors. You’ll see this updated color in the Peek error view and editor squiggles:

#visual studio code #code #java #javascript

What is GEEK

Buddha Community

COMO USAR e trabalhar com Code Review no Visual Studio Code

Não é todo programador que gosta de compartilhar o seu trabalho ou até mesmo receber feedbacks de como o seu código foi escrito, mas o Code Review é cada vez mais comum em empresas do mundo todo.

Conheça uma extensão para Visual Studio Code e comece a trabalhar com Code Review em seu próximo projeto. Essa é a sua chance de saber COMO USAR e trabalhar com Code Review no Visual Studio Code.

#visual studio code #code review #visual studio #code

Visual Studio 2019 v16.7 Preview 2 Available Today!

C++ Updates

Visual Studio v16.7 Preview 2 delivers various improvements in the C++ space. Within the Connection Manager, you’re now able to edit remote SSH connections, e.g. if the IP address of your target system changes and needs to be updated. You’re also able to set default remote connections to be consumed via **${defaultRemoteMachineName} **in CMakeSettings.json and launch.vs.json.

When you edit a remote connection, Visual Studio will no longer need to recopy headers to Windows for a native IntelliSense experience. Likewise, setting default remote connections is useful for checking CMakeSettings.json and launch.vs.json into source control with no user or machine-specific information. These remote connections over SSH allow you to build and debug your C++ projects on a remote Linux system directly from Visual Studio.

C++ Add or Remove SSH Connections with Connection Manager

This release also brings enhanced IntelliSense support for Clang on Windows (clang-cl) in Visual Studio. The clang include path now includes the clang libraries, we’ve improved the display of in-editor squiggles (particularly when using the std library), and we’ve added support for C++2a is supported in clang mode.

The Preview release also contains four new code analysis rules to incorporate additional safety features into C++: C26817, C26818, C26819, and C26820. Please see the C++ Team Blog for more info.

In addition, new C++20 Standard Library features have been implemented. A detailed list is provided in the STL Changelog on GitHub.

.NET Productivity

Quick Info now displays the diagnostic ID along with a help link where you can easily navigate to our documentation to learn more about warnings and errors in your code.

Diagnostic ID with help links in .NET Productivity

Git Productivity

We continue to release more Git functionality in Visual Studio 2019. This time we focus on merge conflict resolution. We’ve revamped the Visual Studio merge editor by decoupling it from TFVC and focusing it on Git.

A new gold info bar at the top of a file will tell you when there are merge conflicts that need to be manually resolved. Clicking will take you to the merge editor, which now has more informative tiles and captions to help you distinguish between the conflicting branches. We’ve reduced the clutter around the zoom margin, health margin, and the toolbar. In addition, it is easier to parse conflicts with aligned matching lines, word level differences, and visible whitespace when it is the only difference. You can turn off non-conflicting differences to just focus on the conflicts. You can also resolve add/add conflicts at the file level now with a two-way merge. Finally, we have added a checkbox to resolve all conflicts on one side or the other with a single click.

Try the new features by toggling the Preview Feature for New Git user experience in Tools > Options.

Improved Git Functionality in Visual Studio 2019 under the Tools Menu

In other Git improvements, we will now close any open folders or solutions before starting a new clone operation, so that Visual Studio can open the newly cloned repo to help you get to your code faster. We’ve improved upon the commit text box, adding inline error checking. And we’ve added UI to help you more clearly understand what is happening when you initialize and push a repository to a remote host like GitHub or Azure Repos.

Local Process with Kubernetes

Local Process with Kubernetes allows you to write, test and debug your .NET code on your development workstation while connected to your Kubernetes cluster with the rest of your application or services. By connecting your development workstation to your cluster, you eliminate the need to manually run and configure dependent services on your development machine. Environment variables, connection strings and volumes from the cluster are available to your microservice code running locally.

For more information on Local Process with Kubernetes, we have detailed it out in our team blog.

#visual studio #announcement #visual studio 2019 #visual studio code

Writing Visual Studio Extensions with Mads - Episode 1: Item Templates

Join Mads Kristensen from the Visual Studio team each week as he builds extensions for Visual Studio live!

#visual studio code #visual studio #code #microsoft #visual studio extensions

Visual Studio Code July 2020

Welcome to the July 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:

• Settings Sync to Stable - Settings Sync is now available for preview in stable.
• Updated Extensions view menu - Simplified menu with additional filtering options.
• New Git View submenus - Refactored overflow menu for Git in the Source Control view.
• Updated in-browser debugging - Debug in the browser without writing a launch configuration.
• Publish a public repository - Choose whether to publish to a public or private GitHub repository.
• Notebook UX updates - New Cell menu, enhanced drag and drop.
• New Remote Container topics - Learn how to attach to a container and create a new dev container.
• Java lightweight mode - Start working with your Java source files more quickly.

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 Monday, August 17 at 9am Pacific (5pm 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. And for the latest Visual Studio Code news, updates, and content, follow us on Twitter @code!

Accessibility#

This milestone, we again received helpful feedback from our community, which helped us identify and tackle accessibility issues.

Workbench#

Search Editor#

We added an Open Search Editor command to open an existing search editor if one exists, or to otherwise create a new one. The pre-existing command Open new Search Editor has been renamed to New Search Editor, and will always create a new Search Editor.

Search Editors also now support custom search.sortOrder configurations, such as sorting by file type, modified date, or result count.

Extensions: Overflow menu cleanup#

The Extensions view filter actions are now displayed under a separate filter action (funnel button):

Theme: GitHub Light

The Extensions view Views and More Actions (…) menu has been refactored for better organization of extension queries (such as Installed or Recommended) and other actions like Check for Extension Updates and Enable All Extensions:

Theme: GitHub Light

Source Control#

Always show repositories#

There’s a new setting, scm.alwaysShowRepositories, that makes the Source Control view always show the repository rows, even if there’s only a single repository open:

Better keyboard navigation#

As you navigate the Source Control view, pressing  Space on a change will now open it as a preview editor and keep the focus in the Source Control view, for easier keyboard navigation.

Git: Overflow menu cleanup#

Thanks to the new submenu proposed API, the Git View and More Actions (…) menu has been refactored for better organization of several commands:

GitHub: Publish to a public repository#

When publishing a repository to GitHub, you now have the option to make the repository public, as opposed to the previous default, private:

Debugging#

UX improvements#

• The default value of the debug.openDebug setting has been changed to openOnFirstSessionStart. As a result, the Debug view will only be automatically opened when the first debug session is started.
• We have updated the debug icon in the Status bar to be better aligned with the icon we use in the Activity bar. This new icon should represent more clearly that the breakpoints will be respected when the program is started this way.
• 

Debug: Open Link command#

A new Debug: Open Link command has been added to quickly debug any URL. Previously, to debug a browser, you had to install the Debugger for Chrome extension and write a launch.json config file to debug a page. This command allows you to debug any URL without needing additional launch configurations.

Theme: Earthsong

If you have a URL selected in your active editor, it will open that automatically. Otherwise, VS Code will prompt you to enter a URL, pre-filling with the URL in your clipboard, if any.

You can adjust the debug configuration used in this command via the debug.javascript.debugByLinkOptions setting.

JavaScript Debugger improvements#

The previous release of VS Code included our new JavaScript debugger. We’d like to thank the community for your feedback on it, and this release includes dozens of resulting fixes and improvements. If you run into any issues with debugging, please make sure to file an issue if you haven’t already.

Browser support#

Text file encoding support#

All of the text file encodings of the desktop version of VS Code are now also supported when running in a browser.

#visual studio code #visual studio #code

User Snippets (Code Shortcuts) in Visual Studio Code

Hello, my friends and fellow developers, this video is all about User Snippets. That means the Snippets (Code Shortcuts) that you can make for yourself. It is a really amazing feature. I hope you like this video

Let me know in the comments below if you want more Visual Studio Code videos or any other videos. And like the video, if you like it.

#visual studio code #visual studio #code