Visual Studio For Mac Showing Files With ~

Posted on  by 

  1. Visual Studio For Mac Tutorial
  2. Visual Studio For Mac Showing Files With C++
  3. Visual Studio For Mac Wiki
  4. Visual Studio For Mac Showing Files With Tfs
  5. Visual Studio For Mac Download
-->
  • I use Visual Studio for Mac with Unity3d. We delete assets from Unity project regularly and each time I delete something, I get the following message multiple times on Visual Studio.
  • Git is the most popular version control system today. It enables distributed version control for modern web apps. Sometimes, you want to be able to re-trace your code to its previous versions and restore that version. The Git History extension gives you the complete Git history, including a history of inline files, all within Visual Studio Code.

Today I will show you how to get started with setting up your.NET development environment on a Mac running Yosemite and show you how to build a Console and an ASP.NET MVC 6 call log application using Visual Studio Code and ASP.NET 5.

Developer Community |System Requirements |Compatibility |Distributable Code |Xamarin |Blogs |Servicing |

Click the button to download the latest version of Visual Studio 2017 for Mac. For instructions on setup and install, see the Setup and Install Visual Studio for Mac documentation.

To learn more about Visual Studio 2017 for Mac, see Mac System Requirements and Mac Platform Targeting and Compatibility.

To learn more about other related downloads, see the Downloads page.

What's New in 7.8

Visual Studio 2017 for Mac version 7.8 Releases

  • May 13, 2019 – Visual Studio 2017 for Mac version 7.8.4
  • March 12, 2019 – Visual Studio 2017 for Mac version 7.8.3
  • February 28, 2019 – Visual Studio 2017 for Mac version 7.8.2
  • February 22, 2019 – Visual Studio 2017 for Mac version 7.8.1
  • February 20, 2019 – Visual Studio 2017 for Mac version 7.8

Release Highlights

This release focuses on improving the quality in Visual Studio for Mac through bug fixes, performance improvements, and reliability improvements.

We also updated the version of NuGet to 4.8, .NET Core SDK to 2.1.504, and .NET Core Runtime 2.1.8

Visual Studio 2017 for Mac version 7.8 (7.8.0.1624)

released February 20, 2019

Shell

  • We fixed an issue where custom key bindings for Remove Unused and Sort (Usings) don't work.
  • We fixed an issue where switching from the application and returning, does not focus on the editor correctly.
  • We fixed an issue where the cursor in editor window is lost when switching applications.
  • We fixed an issue where focusing out/into Visual Studio changes the default focused element on the UI.
  • We fixed an issue where Visual Studio for Mac would fail to track file changes for files in certain folders.
  • We fixed an issue where Visual Studio for Mac doesn't remember opened files.
  • We fixed an issue where the Toolbar selector for build configuration is disabled.
  • We fixed an issue where adding a new folder to a project does not allow instant renaming.
  • We fixed an issue where Start Debugging after Start without Debugging results in an exception for ASP.Net projects.
  • We fixed a performance issue with build output search.
  • The Run Item command on the Solution Explorer has been renamed to Run Project.
  • We fixed an issue where the welcome page is shown when loading a solution from finder.

.NET Core

  • We updated to .NET Core 2.1.8 to include a security update.
  • We fixed an issue where the create button doesn't create new project for .NET Core 3.0 preview 2.
  • We fixed an issue where .NET Core 3.0 can be selected in the New Project dialog when it is not supported.
  • We removed the VB.NET option from .NET Core projects.

ASP.NET Core

  • We fixed an issue where the Folder profile would be created with 'Default' configuration instead of 'Release'.

Web Tools

  • We fixed an issue where Publish to Azure creates a profile with the wrong name.
  • We fixed an issue where application arguments are not passed to the Azure Functions host.
  • We added the following additional Azure Functions templates
    • CosmosDB trigger
    • EventHub trigger
    • IoT Hub trigger
    • SendGrid trigger
    • ServiceBus Queue trigger
    • ServiceBus Topic trigger
  • We fixed an issue where it was not possible to publish to Azure API App instances.

Xamarin

  • We updated the Xamarin Test Cloud agent NuGet version.
  • We fixed an issue where the View Archives command would appear in .NET Core projects.

Xamarin.Forms

  • IntelliSense in Xamarin.Forms XAML files for FontFamily is now available.

Designers

  • We fixed an issue where the toolbox regressed Android designer usage.
  • We fixed an issue when attempting to drag and drop controls to iOS storyboards from the Tool Box after searching for controls does not work.

Xamarin.Android

  • We fixed an issue where the JDK notification was shown on the welcome page, even for non-Android projects.
  • We fixed an issue where launching Visual Studio for Mac without any Java installed shows 2 system prompts to install Java.
  • We fixed an issue where the Android resource update could occur at the same time as a build which could then cause build issues.
  • We fixed an issue where Visual Studio for Mac would fail to upload APK to Acer Chromebook R11.
  • We fixed an issue where new Android apps have uppercase letters in the package name.
  • We fixed an issue where 'Your project is not referencing the 'Mono.Android.Version=v8.1' framework' when AndroidUseLatestPlatformSDK is true.
  • We fixed an issue where Visual Studio for Mac does not recognize AndroidManifest in specific build configurations..
  • We fixed an issue where opening the Report A Problem dialog also displays 'Install JDK' dialog.
  • We fixed an issue where the Google Play SDK warning is shown even when publishing Ad-Hoc.

Xamarin.iOS

  • It is now possible to choose .pdf files for image assets that do not support vector images.
  • We fixed an issue where Visual Studio for Mac erroneously indicates that a Xamarin.Mac property is unavailable.
  • We fixed an issue where it is not possible to choose devices for named colors in the asset catalog.
  • We fixed an issue where the iOS simulator is no longer brought to front when starting a debug session.
  • We fixed an issue where Native References not working in iOS library projects and appear to be ignored.
  • We fixed an issue where deleting a Native Reference does not delete the the file on disk.
  • We fixed an issue where the Debugger doesn't connect to a keyboard extension on any device.

Xamarin.Mac

  • We fixed an issue where .xib templates seem to need customObjectInstantitationMethod='direct' added.
  • We fixed an issue where it is not possible to change the target framework version for Xamarin.Mac full on re-opening project options.
  • We fixed an issue where the project options for a Mac build (classic) shows incorrect UI.

Code Editor

  • We fixed an issue where the code fix preview window is too small.
  • We fixed an issue where error squiggles were not up to date.
  • We fixed an issue where the editor would freeze while typing
  • We fixed an issue where Changing the tab would not allow you to search a file
  • We fixed an issue where Using statement indenting is incorrect.
  • We fixed an issue where Roslyn throws a fatal exception (System.ArgumentOutOfRangeException).
  • We fixed an issue where formatting of parameters across multiple lines is incorrect.
  • We fixed an issue where the constructor generator would cause Visual Studio for Mac to crash.
  • We fixed an issue where smart semicolon placement causes incorrect semicolon placement.
  • We fixed an issue where typing can be slow in large files when accessibility is enabled.
  • We fixed an issue where a fatal error can occur when trying to navigate inside the editor using VoiceOver.
  • We fixed an issue where the caret location in quick fix margin is incorrect.
  • We fixed a performance issue where indent correcting is taking up too much time on large files.
  • We fixed an issue where Intellisense soft-selection is confusing.
  • We fixed an issue where Visual Studio for Mac can't open .targets files.
  • We fixed an issue where the display updates partially when commenting a collapsed method.
  • We fixed an issue where C# syntax highlight doesn't work for some of the keywords.
  • We fixed an issue where invoking some snippets from the toolbox in .cs files leads to poorly formatted code.
  • We fixed an issue where pressing Down to choose the closing tag completion in XAML IntelliSense closes the completion window.
  • We fixed an issue where the file 'redacted' could not be opened.
  • We fixed an issue where sometimes pasting fails in XAML files.
  • We fixed an issue where, when adding an attribute via Intellisense, it does not trim 'Attribute' from the name.
  • We fixed an issue where code suggestion does the wrong thing when ( is pressed after a stray arrow key.

NuGet

  • We fixed an issue where Visual Studio for Mac crashes after 'Could not add packages' error.
  • We updated the version of NuGet to 4.8.
  • NuGet package diagnostic warnings are now shown in the Solution Explorer. Any diagnostics warnings will be rendered with a warning icon and the full text of the warning available as a tool tip.
  • We fixed a set of issues with NuGet:
    • problem while restoring NuGet packages which don't have stable version.
    • The VS4Mac bundle nuget version is too old: 4.3.1.
    • Referencing packages conditionally using variable does not work correctly.
    • Xamarin.Forms app with multi target framework library referenced fail to build.
    • Visual Studio Mac Csproj build not support Item contidion.
    • Support conditional NuGet PackageReferences in multi-targeting projects.
    • Show per-framework dependencies when multi-targeting.
    • VS cannot build F# dotnet core solution.
    • Nuget restore ignore build targets.
    • NuGet restores the wrong version of Microsoft.AspNetCore.App.

Debugger

  • We fixed an issue where the debugger would fail when running on an external console on Mojave.
For

Test Tools

  • We fixed an issue where xUnit Fact 'DisplayName' not shown in test explorer if the name has a period at the end.
  • We fixed an issue where the text editor unit test integration ('Unit test 'name' could not be loaded') would fail.
  • We fixed a performance issue where the 'Test Results' pane has bad performance when very large amounts of text are shown.
  • We fixed an issue where the unit test integration in the editor does not properly trigger test cases.
  • We fixed an issue that could cause xunit to fail to restore.

F#

  • We fixed an issue where open statements for F# must be manually added when pasting/writing code.
  • We fixed an issue where new F# projects shows IntelliSense errors.
  • We fixed an issue for F# projects where Visual Studio for Mac overwrites the project GUID to be lowercase instead of uppercase.

Project System

  • We fixed an issue where the copy & paste of a XAML file causes a disassociation between the .xaml and .xaml.cs files.
  • We fixed an issue where files are being added to ItemGroup.Compile(Remove) and this related issue - Error type of namespace not found.
  • We fixed an issue where an invalid C# file is created with a new library project.
  • We fixed an issue where it is not possible to create a culture specific .resx file through the 'New File ..' menu in the Solutions Explorer context menu.

Assembly Browser

  • We fixed an issue where the Assembly Browser shows the wrong icon for properties.
  • We fixed an issue where System.DayOfWeek enum (Wednesday) does not appear to be assigned a value.

Accessibility

  • We fixed a number of accessibility issues in this release, including several VoiceOver issues in the Debugger and in creating iOS developer certificates, and Keyboard issues in the Android SDK Manager.

Other

  • We fixed an issue where unchecking the Organize Using > Place System directives first setting does not save.
  • We fixed an issue where Visual Studio for Mac is not remembering settings.
  • We fixed an issue where Checking for updates can result in multiple prompts to sign in.

Visual Studio 2017 for Mac version 7.8.1.4

released February 22, 2019

  • We fixed an issue where Visual Studio for Mac becomes unresponsive when selecting two column view.

Visual Studio 2017 for Mac version 7.8.2.1

released February 28, 2019

  • We fixed an issue where Debugger features sometimes don't work as expected with Unity.

Visual Studio 2017 for Mac version 7.8.3.2

released March 12, 2019

  • This release contains an updated 4.8 NuGet Client, which in turn closes a NuGet Client vulnerability.
  • We fixed an issue where Using Git to publish an existing project to a new remote repository was not working.
  • We fixed an issue where Git remote operations were failing in Visual Studio for Mac:.
  • We fixed an issue where Tooltips not being shown for F# solutions.
  • We fixed an issue where The Report a Problem dialog crashes Visual Studio for Mac when entering details.
  • We fixed an issue where Visual Studio for Mac crashes while using Report a Problem if the debugger connection is lost.
  • We fixed an issue where Two sign in popup windows would show if you weren't signed in and tried to Report a Problem.
  • We fixed an issue causing warnings about missing icons to show up in the log files when using Report a Problem.
  • We fixed an issue preventing build messages from displaying in the Build Output window after building Docker Compose projects.

Visual Studio 2017 for Mac version 7.8.4.1

released May 13, 2019

  • This release fixes an issue where (Visual Studio for Mac 7.8.3 crashes after loading a second solution)[https://developercommunity.visualstudio.com/content/problem/509716/visual-studio-783-build2-crashes-after-loading-a-s.html].

Feedback

We would love to hear from you! You can report a problem through the Report a Problem option in the Visual Studio for Mac IDE, and track your feedback in the Developer Community portal. For suggesting new features you can use Suggest a Feature, these are also tracked in the Developer Community.

Blogs

Take advantage of the insights and recommendations available in the Developer Tools Blogs site to keep you up-to-date on all new releases and include deep dive posts on a broad range of features.

Visual Studio 2017 for Mac Release Notes History

You can view prior versions of Visual Studio 2017 for Mac release notes on the Release notes history page.

Top of Page

At its heart, Visual Studio Code is a code editor. Like many other code editors, VS Code adopts a common user interface and layout of an explorer on the left, showing all of the files and folders you have access to, and an editor on the right, showing the content of the files you have opened.

Basic Layout

VS Code comes with a simple and intuitive layout that maximizes the space provided for the editor while leaving ample room to browse and access the full context of your folder or project. The UI is divided into five areas:

  • Editor - The main area to edit your files. You can open as many editors as you like side by side vertically and horizontally.
  • Side Bar - Contains different views like the Explorer to assist you while working on your project.
  • Status Bar - Information about the opened project and the files you edit.
  • Activity Bar - Located on the far left-hand side, this lets you switch between views and gives you additional context-specific indicators, like the number of outgoing changes when Git is enabled.
  • Panels - You can display different panels below the editor region for output or debug information, errors and warnings, or an integrated terminal. Panel can also be moved to the right for more vertical space.

Each time you start VS Code, it opens up in the same state it was in when you last closed it. The folder, layout, and opened files are preserved.

Open files in each editor are displayed with tabbed headers (Tabs) at the top of the editor region. To learn more about tabbed headers, see the Tabs section below.

Tip: You can move the Side Bar to the right hand side (View > Move Side Bar Right) or toggle its visibility (⌘B (Windows, Linux Ctrl+B)).

Side by side editing

You can open as many editors as you like side by side vertically and horizontally. If you already have one editor open, there are multiple ways of opening another editor to the side of the existing one:

  • Alt click on a file in the Explorer.
  • ⌘ (Windows, Linux Ctrl+) to split the active editor into two.
  • Open to the Side (⌃Enter (Windows, Linux Ctrl+Enter)) from the Explorer context menu on a file.
  • Click the Split Editor button in the upper right of an editor.
  • Drag and drop a file to any side of the editor region.
  • Ctrl+Enter (macOS: Cmd+Enter) in the Quick Open (⌘P (Windows, Linux Ctrl+P)) file list.

Whenever you open another file, the editor that is active will display the content of that file. So if you have two editors side by side and you want to open file 'foo.cs' into the right-hand editor, make sure that editor is active (by clicking inside it) before opening file 'foo.cs'.

By default editors will open to the right-hand side of the active one. You can change this behavior through the setting workbench.editor.openSideBySideDirection and configure to open new editors to the bottom of the active one instead.

When you have more than one editor open you can switch between them quickly by holding the Ctrl (macOS: Cmd) key and pressing 1, 2, or 3.

Tip: You can resize editors and reorder them. Drag and drop the editor title area to reposition or resize the editor.

Minimap

A Minimap (code outline) gives you a high-level overview of your source code which is very useful for quick navigation and code understanding. A file's minimap is shown on the right side of the editor. You can click or drag the shaded area to quickly jump to different sections of your file.

Tip: You can move the minimap to the left hand side or disable it completely by respectively setting 'editor.minimap.side': 'left' or 'editor.minimap.enabled': false in your user or workspace settings.

Indent Guides

The image above also shows indentation guides (vertical lines) which help you quickly see matching indent levels. If you would like to disable indent guides, you can set 'editor.renderIndentGuides': false in your user or workspace settings.

Explorer

The Explorer is used to browse, open, and manage all of the files and folders in your project. VS Code is file and folder based - you can get started immediately by opening a file or folder in VS Code.

After opening a folder in VS Code, the contents of the folder are shown in the Explorer. You can do many things from here:

  • Create, delete, and rename files and folders.
  • Move files and folders with drag and drop.
  • Use the context menu to explore all options.

Tip: You can drag and drop files into the Explorer from outside VS Code to copy them (if the explorer is empty VS Code will open them instead)

VS Code works very well with other tools that you might use, especially command-line tools. If you want to run a command-line tool in the context of the folder you currently have open in VS Code, right-click the folder and select Open in Command Prompt (or Open in Terminal on macOS or Linux).

You can also navigate to the location of a file or folder in the native Explorer by right-clicking on a file or folder and selecting Reveal in Explorer (or Reveal in Finder on the macOS or Open Containing Folder on Linux).

Tip: Type ⌘P (Windows, Linux Ctrl+P) (Quick Open) to quickly search and open a file by its name.

By default, VS Code excludes some folders from the Explorer (for example. .git). Use the files.excludesetting to configure rules for hiding files and folders from the Explorer.

Tip: This is really useful to hide derived resources files, like *.meta in Unity, or *.js in a TypeScript project. For Unity to exclude the *.cs.meta files, the pattern to choose would be: '**/*.cs.meta': true. For TypeScript, you can exclude generated JavaScript for TypeScript files with: '**/*.js': {'when': '$(basename).ts'}.

Multi-selection

You can select multiple files in the File Explorer and OPEN EDITORS view to run actions (Delete, Drag and Drop, Open to the Side) on multiple items. Use the Ctrl/Cmd key with click to select individual files and Shift + click to select a range. If you select two items, you can now use the context menu Compare Selected command to quickly diff two files.

Note: In earlier VS Code releases, clicking with the Ctrl/Cmd key pressed would open a file in a new Editor Group to the side. If you would still like this behavior, you can use the workbench.list.multiSelectModifier setting to change multi-selection to use the Alt key.

Outline view

The Outline view is a separate section in the bottom of the File Explorer. When expanded, it will show the symbol tree of the currently active editor.

The Outline view has different Sort By modes, optional cursor tracking, and supports the usual open gestures. It also includes an input box which finds or filters symbols as you type. Errors and warnings are also shown in the Outline view, letting you see at a glance a problem's location.

For symbols, the view relies on information computed by your installed extensions for different file types. For example, the built-in Markdown support returns the Markdown header hierarchy for a Markdown file's symbols.

There are several Outline view settings which allow you to enable/disable icons and control the errors and warnings display (all enabled by default):

  • outline.icons - Toggle rendering outline elements with icons.
  • outline.problems.enabled - Show errors and warnings on outline elements.
  • outline.problems.badges - Toggle using badges for errors and warnings.
  • outline.problems.colors - Toggle using colors for errors and warnings.

Open Editors

At the top of the Explorer is a view labeled OPEN EDITORS. This is a list of active files or previews. These are files you previously opened in VS Code that you were working on. For example, a file will be listed in the OPEN EDITORS view if you:

  • Make a change to a file.
  • Double-click a file's header.
  • Double-click a file in the Explorer.
  • Open a file that is not part of the current folder.

Just click an item in the OPEN EDITORS view, and it becomes active in VS Code.

Once you are done with your task, you can remove files individually from the OPEN EDITORS view, or you can remove all files by using the View: Close All Editors or View: Close All Editors in Group actions.

Views

The File Explorer is just one of the Views available in VS Code. There are also Views for:

  • Search - Provides global search and replace across your open folder.
  • Source Control - VS Code includes Git source control by default.
  • Debug - VS Code's Debug View displays variables, call stacks, and breakpoints.
  • Extensions - Install and manage your extensions within VS Code.
  • Custom views - Views contributed by extensions under Explorer and Debug views.

Tip: You can open any view using the View: Open View command.

You can show or hide views from within the main view and also reorder them by drag and drop.

Activity Bar

The Activity Bar on the left lets you quickly switch between Views. You can also reorder Views by dragging and dropping them on the Activity Bar or remove a View entirely (right click Hide from Activity Bar).

Command Palette

VS Code is equally accessible from the keyboard. The most important key combination to know is ⇧⌘P (Windows, Linux Ctrl+Shift+P), which brings up the Command Palette. From here, you have access to all of the functionality of VS Code, including keyboard shortcuts for the most common operations.

The Command Palette provides access to many commands. You can execute editor commands, open files, search for symbols, and see a quick outline of a file, all using the same interactive window. Here are a few tips:

  • ⌘P (Windows, Linux Ctrl+P) will let you navigate to any file or symbol by typing its name
  • ⌃⇧Tab (Windows, Linux Ctrl+Shift+Tab) will cycle you through the last set of files opened
  • ⇧⌘P (Windows, Linux Ctrl+Shift+P) will bring you directly to the editor commands
  • ⇧⌘O (Windows, Linux Ctrl+Shift+O) will let you navigate to a specific symbol in a file
  • ⌃G (Windows, Linux Ctrl+G) will let you navigate to a specific line in a file

Type ? into the input field to get a list of available commands you can execute from here:

Configuring the editor

VS Code gives you many options to configure the editor. From the View menu, you can hide or toggle various parts of the user interface, such as the Side Bar, Status Bar, and Activity Bar.

Hide the Menu Bar (Windows, Linux)

You can hide the Menu Bar on Windows and Linux with the View > Toggle Menu Bar command. You can still access the Menu Bar by pressing the Alt key (window.menuBarVisibility setting).

Settings

Most editor configurations are kept in settings which can be modified directly. You can set options globally through user settings or per project/folder through workspace settings. Settings values are kept in a settings.jsonfile.

  • Select File > Preferences > Settings (or press ⌘, (Windows, Linux Ctrl+,)) to edit the user settings.json file.
  • To edit workspace settings, select the WORKSPACE SETTINGS tab to edit the workspace settings.json file.

Note for macOS users: The Preferences menu is under Code not File. For example, Code > Preferences > Settings.

You will see the VS Code Default Settings in the left window and your editable settings.json on the right. You can easily filter settings in the Default Settings using the search box at the top. Copy a setting over to the editable settings.json on the right by clicking on the edit icon to the left of the setting. Settings with a fixed set of values allow you to pick a value as part of their edit icon menu.

After editing your settings, type ⌘S (Windows, Linux Ctrl+S) to save your changes. The changes will take effect immediately.

Note: Workspace settings will override User settings and are useful for sharing project specific settings across a team.

Zen Mode

Zen Mode lets you focus on your code by hiding all UI except the editor (no Activity Bar, Status Bar, Side Bar and Panel), going to full screen and centering the editor layout. Zen mode can be toggled using View menu, Command Palette or by the shortcut ⌘K Z (Windows, Linux Ctrl+K Z). Double Esc exits Zen Mode. The transition to full screen can be disabled via zenMode.fullScreen. Zen Mode can be further tuned by the following settings: zenMode.hideStatusBar, zenMode.hideTabs, zenMode.fullScreen, zenMode.restore, and zenMode.centerLayout.

Centered editor layout

Centered editor layout allows you to center align the editor area. This is particularly useful when working with a single editor on a large monitor. You can use the sashes on the side to resize the view (hold down the Alt key to independently move the sashes).

Tabs

Visual Studio Code shows open items with Tabs (tabbed headings) in the title area above the editor.

When you open a file, a new Tab is added for that file.

Tabs let you quickly navigate between items and you can Drag and Drop Tabs to reorder them.

When you have more open items than can fit in the title area, you can use the Show Opened Editors command (available through the ... More button) to display a drop-down list of tabbed items.

If you don't want to use Tabs, you can disable the feature by setting the workbench.editor.showTabssetting to false:

See the section below to optimize VS Code when working without Tabs.

Tab ordering

By default, new Tabs are added to the right of the existing Tabs but you can control where you'd like new Tabs to appear with the workbench.editor.openPositioning setting.

For example, you might like new tabbed items to appear on the left:

Preview mode

When you single-click or select a file in the Explorer, it is shown in a preview mode and reuses an existing Tab. This is useful if you are quickly browsing files and don't want every visited file to have its own Tab. When you start editing the file or use double-click to open the file from the Explorer, a new Tab is dedicated to that file.

Preview mode is indicated by italics in the Tab heading:

If you'd prefer to not use preview mode and always create a new Tab, you can control the behavior with these settings:

  • workbench.editor.enablePreview to globally enable or disable preview editors
  • workbench.editor.enablePreviewFromQuickOpen to enable or disable preview editors when opened from Quick Open

Editor Groups

When you split an editor (using the Split Editor or Open to the Side commands), a new editor region is created which can hold a group of items. You can open as many editor regions as you like side by side vertically and horizontally.

You can see these clearly in the OPEN EDITORS section at the top of the Explorer view:

You can Drag and Drop editor groups on the workbench, move individual Tabs between groups and quickly close entire groups (Close All).

Note: VS Code uses editor groups whether or not you have enabled Tabs. Without Tabs, editor groups are a stack of your open items with the most recently selected item visible in the editor pane.

Grid editor layout

By default, editor groups are laid out in vertical columns (for example when you split an editor to open it to the side). You can easily arrange editor groups in any layout you like, both vertically and horizontally:

To support flexible layouts, you can create empty editor groups. By default, closing the last editor of an editor group will also close the group itself, but you can change this behavior with the new setting workbench.editor.closeEmptyGroups: false:

There are a predefined set of editor layouts in the new View > Editor Layout menu:

Editors that open to the side (for example by clicking the editor toolbar Split Editor action) will by default open to the right-hand side of the active editor. If you prefer to open editors below the active one, configure the new setting workbench.editor.openSideBySideDirection: down.

There are many keyboard commands for adjusting the editor layout with the keyboard alone, but if you prefer to use the mouse, drag and drop is a fast way to split the editor into any direction:

Pro Tip: If you press and hold the Alt key while hovering over the toolbar action to split an editor, it will offer to split to the other orientation. This is a fast way to split either to the right or to the bottom.

Keyboard shortcuts

Here are some handy keyboard shortcuts to quickly navigate between editors and editor groups.

If you'd like to modify the default keyboard shortcuts, see Key Bindings for details.

  • ⌥⌘→ (Windows, Linux Ctrl+PageDown) go to the right editor.
  • ⌥⌘← (Windows, Linux Ctrl+PageUp) go to the left editor.
  • ⌃Tab (Windows, Linux Ctrl+Tab) open the next editor in the editor group MRU list.
  • ⌃⇧Tab (Windows, Linux Ctrl+Shift+Tab) open the previous editor in the editor group MRU list.
  • ⌘1 (Windows, Linux Ctrl+1) go to the leftmost editor group.
  • ⌘2 (Windows, Linux Ctrl+2) go to the center editor group.
  • ⌘3 (Windows, Linux Ctrl+3) go to the rightmost editor group.
  • go to the previous editor group.
  • go to the next editor group.
  • ⌘W (Windows Ctrl+F4, Linux Ctrl+W) close the active editor.
  • ⌘K W (Windows, Linux Ctrl+K W) close all editors in the editor group.
  • ⌘K ⌘W (Windows, Linux Ctrl+K Ctrl+W) close all editors.

Working without Tabs

If you prefer not to use Tabs (tabbed headings), you can disable Tabs (tabbed headings) entirely by setting workbench.editor.showTabs to false.

Disable Preview mode

Without Tabs, the OPEN EDITORS section of the File Explorer is a quick way to do file navigation. With preview editor mode, files are not added to the OPEN EDITOR list nor editor group on single-click open. You can disable this feature through the workbench.editor.enablePreview and workbench.editor.enablePreviewFromQuickOpen settings.

Ctrl+Tab to navigate in entire editor history

You can change keybindings for Ctrl+Tab to show you a list of all opened editors from the history independent from the active editor group.

Edit your keybindings and add the following:

Close an entire group instead of a single editor

Visual Studio For Mac Tutorial

If you liked the behavior of VS Code closing an entire group when closing one editor, you can bind the following in your keybindings.

macOS:

Showing

Windows/Linux:

Window management

VS Code has some options to control how windows (instances) should be opened or restored between sessions.

The settings window.openFoldersInNewWindow and window.openFilesInNewWindow are provided to configure opening new windows or reusing the last active window for files or folders and possible values are default, on and off.

If configured to be default, we will make the best guess about reusing a window or not based on the context from where the open request was made. Flip this to on or off to always behave the same. For example, if you feel that picking a file or folder from the File menu should always open into a new window, set this to on.

Visual Studio For Mac Showing Files With C++

Note: There can still be cases where this setting is ignored (for example, when using the -new-window or -reuse-window command-line option).

The window.restoreWindows setting tells VS Code how to restore the opened windows of your previous session. By default, VS Code will reopen the last opened window you worked on (setting: one). Change this setting to none to never reopen any windows and always start with an empty VS Code instance. Change it to all to restore all windows you worked on during your previous session or folders to only restore windows that had folders opened.

Next steps

Now that you know the overall layout of VS Code, start to customize the editor to how you like to work by looking at the following topics:

  • Changing the Theme - Set a Color and/or File Icon theme to your preference.

Common questions

Visual Studio For Mac Wiki

How can I change the color of the indent guides?

The indent guide colors are customizable as are most VS Code UI elements. To customize the indent guides color for your active color theme, use the workbench.colorCustomizationssetting and modify the editorIndentGuide.background value.

Visual Studio For Mac Showing Files With Tfs

For example, to make the indent guides bright blue, add the following to your settings.json:

Can I hide the OPEN EDITORS section in the Explorer?

Visual Studio For Mac Download

Yes, you can hide the OPEN EDITORS list with the explorer.openEditors.visiblesetting, which declares how many items to display before a scroll bar appears. Setting 'explorer.openEditors.visible': 0 will hide OPEN EDITORS when you have an open folder. The list will still be displayed if you are using VS Code to view loose files.

Coments are closed
Acdsee Photo Studio For Mac 4 Review Image Line Fl Studio 12 Fruity Edition For Mac