Return to site

Visual Studio For Mac And Linux

broken image


Our docs contain a Common questions section as needed for specific topics. We've captured items here that don't fit in the other topics.

If you don't see an answer to your question here, check our previously reported issues on GitHub and our release notes.

What is the difference between Visual Studio Code and Visual Studio IDE?

The problem you might have is that Command and Alt/Option keys are swapped between Mac and PC keyboards. On a Mac, Command is next to space bar and on PC this is usually Alt key. I followed the answer given by Nimeshka and added two steps: Replace alt with super (Linux name for Windows/Command key) Replace cmd with alt; Feel free to use my. This topic applies to installation of Visual Studio on Windows. Visual Studio Code is a lightweight, cross-platform development environment that runs on Windows, Mac, and Linux systems. The Microsoft C/C for Visual Studio Code extension supports IntelliSense, debugging, code formatting, auto-completion. Visual Studio for Mac doesn't support Microsoft C, but does support.NET. Visual Studio for Mac.NET. Azure DevOps Server (TFS) 0. MSVC for mac (and linux) visual studio for mac. Shammi Mohamed reported Apr 05, 2019 at 09:38 AM. Show comments 2. Add comment 10 40000 characters.

Microsoft Visual Studio For Mac

Visual Studio Code is a streamlined code editor with support for development operations like debugging, task running, and version control. It aims to provide just the tools a developer needs for a quick code-build-debug cycle and leaves more complex workflows to fuller featured IDEs, such as Visual Studio IDE.

Which OSs are supported?

VS Code runs on macOS, Linux, and Windows. See the Requirements documentation for the supported versions. You can find more platform specific details in the Setup overview.

Is VS Code free?

Yes, VS Code is free for private or commercial use. See the product license for details.

How to disable telemetry reporting

VS Code collects usage data and sends it to Microsoft to help improve our products and services. Read our privacy statement and telemetry documentation to learn more.

If you don't wish to send usage data to Microsoft, you can set the telemetry.enableTelemetry user setting to false.

From File > Preferences > Settings (macOS: Code > Preferences > Settings), search for telemetry, and uncheck the Telemetry: Enable Telemetry setting. This will silence all telemetry events from VS Code going forward.

Important Notice: VS Code gives you the option to install Microsoft and third party extensions. These extensions may be collecting their own usage data and are not controlled by the telemetry.enableTelemetry setting. Consult the specific extension's documentation to learn about its telemetry reporting.

How to disable crash reporting

VS Code collects data about any crashes that occur and sends it to Microsoft to help improve our products and services. Read our privacy statement and telemetry documentation to learn more.

If you don't wish to send crash data to Microsoft, you can change the enable-crash-reporter runtime argument to false

  • Open the Command Palette (⇧⌘P (Windows, Linux Ctrl+Shift+P)).
  • Run the Preferences: Configure Runtime Arguments command.
  • This command will open a argv.json file to configure runtime arguments.
  • Edit 'enable-crash-reporter': false.
  • Restart VS Code.

GDPR and VS Code

Visual Studio For Mac And Linux

Now that the General Data Protection Regulation (GDPR) is in effect, we want to take this opportunity to reiterate that we take privacy very seriously. That's both for Microsoft as a company and specifically within the VS Code team.

To support GDPR:

  • The VS Code product notifies all users that they can opt out of telemetry collection.
  • The team actively reviews and classifies all telemetry sent (documented in our OSS codebase).
  • There are valid data retention policies in place for any data collected, for example crash dumps.

You can learn more about VS Code's GDPR compliance in the telemetry documentation.

What online services does VS Code use?

Beyond crash reporting and telemetry, VS Code uses online services for various other purposes such as downloading product updates, finding, installing, and updating extensions, or providing Natural Language Search within the Settings editor. You can learn more in Managing online services.

You can choose to turn on/off features that use these services. From File > Preferences > Settings (macOS: Code > Preferences > Settings), and type the tag @tag:usesOnlineServices. This will display all settings that control the usage of online services and you can individually switch them on or off.

How do I opt out of VS Code auto-updates?

By default, VS Code is set up to auto-update for macOS and Windows users when we release new updates. If you do not want to get automatic updates, you can set the Update: Mode setting from default to none.

To modify the update mode, go to File > Preferences > Settings (macOS: Code > Preferences > Settings), search for update mode and change the setting to none.

If you use the JSON editor for your settings, add the following line:

You can install a previous release of VS Code by uninstalling your current version and then installing the download provided at the top of a specific release notes page.

Note: On Linux: If the VS Code repository was installed correctly then your system package manager should handle auto-updating in the same way as other packages on the system. See Installing VS Code on Linux.

Opt out of extension updates

By default, VS Code will also auto-update extensions as new versions become available. If you do not want extensions to automatically update, you can clear the Extensions: Auto Update check box in the Settings editor (⌘, (Windows, Linux Ctrl+,)).

If you use the JSON editor to modify your settings, add the following line:

Licensing

Location

You can find the VS Code licenses, third party notices and Chromium Open Source credit list under your VS Code installation location resourcesapp folder. VS Code's ThirdPartyNotices.txt, Chromium's Credits_*.html, and VS Code's English language LICENSE.txt are available under resourcesapp. Localized versions of LICENSE.txt by Language ID are under resourcesapplicenses.

Why does Visual Studio Code have a different license than the vscode GitHub repository?

To learn why Visual Studio Code, the product, has a different license than the open-source vscode GitHub repository, see issue #60 for a detailed explanation.

What is the difference between the vscode repository and the Microsoft Visual Studio Code distribution?

The github.com/microsoft/vscode repository (Code - OSS) is where we develop the Visual Studio Code product. Not only do we write code and work on issues there, we also publish our roadmap and monthly iteration and endgame plans. The source code is available to everyone under a standard MIT license.

Visual Studio Code is a distribution of the Code - OSS repository with Microsoft specific customizations (including source code), released under a traditional Microsoft product license.

See the Visual Studio Code and 'Code - OSS' Differences article for more details.

What does 'Built on Open Source' mean?

Microsoft Visual Studio Code is a Microsoft licensed distribution of 'Code - OSS' that includes Microsoft proprietary assets (such as icons) and features (Visual Studio Marketplace integration, small aspects of enabling Remote Development). While these additions make up a very small percentage of the overall distribution code base, it is more accurate to say that Visual Studio Code is 'built' on open source, rather than 'is' open source, because of these differences. More information on what each distribution includes can be found in the Visual Studio Code and 'Code - OSS' Differences article.

How do I find the license for an extension?

Most extensions link to their license on their Marketplace page or in the overview section, when you select an extension in the Extensions view.

For example:

If you don't find a link to the license, you may find a license in the extension's repository if it is public, or you can contact the extension author through the Q & A section of the Marketplace.

Visual Studio In Mac

Are all VS Code extensions open source?

Extension authors are free to choose a license that fits their business needs. While many extension authors have opted to release their source code under an open-source license, some extensions like Wallaby.js, Google Cloud Code, and the VS Code Remote Development extensions use proprietary licenses.

At Microsoft, we open source our extensions whenever possible. However, reliance on existing proprietary source code or libraries, source code that crosses into Microsoft licensed tools or services (for example Visual Studio), and business model differences across the entirety of Microsoft will result in some extensions using a proprietary license. You can find a list of Microsoft contributed Visual Studio Code extensions and their licenses in the Microsoft Extension Licenses article.

How do I find the version?

You can find the VS Code version information in the About dialog box.

On macOS, go to Code > About Visual Studio Code.

On Windows and Linux, go to Help > About.

The VS Code version is the first Version number listed and has the version format 'major.minor.release', for example '1.27.0'.

Previous release versions

You can find links to some release downloads at the top of a version's release notes:

If you need a type of installation not listed there, you can manually download via the following URLs:

Download typeURL
Windows 64 bit System installerhttps://update.code.visualstudio.com/{version}/win32-x64/stable
Windows 64 bit User installerhttps://update.code.visualstudio.com/{version}/win32-x64-user/stable
Windows 64 bit ziphttps://update.code.visualstudio.com/{version}/win32-x64-archive/stable
Windows 64 bit ARM System installerhttps://update.code.visualstudio.com/{version}/win32-arm64/stable
Windows 64 bit ARM User installerhttps://update.code.visualstudio.com/{version}/win32-arm64-user/stable
Windows 64 bit ARM ziphttps://update.code.visualstudio.com/{version}/win32-arm64-archive/stable
Windows 32 bit System installerhttps://update.code.visualstudio.com/{version}/win32/stable
Windows 32 bit User installerhttps://update.code.visualstudio.com/{version}/win32-user/stable
Windows 32 bit ziphttps://update.code.visualstudio.com/{version}/win32-archive/stable
macOShttps://update.code.visualstudio.com/{version}/darwin/stable
Linux 64 bithttps://update.code.visualstudio.com/{version}/linux-x64/stable
Linux 64 bit debianhttps://update.code.visualstudio.com/{version}/linux-deb-x64/stable
Linux 64 bit rpmhttps://update.code.visualstudio.com/{version}/linux-rpm-x64/stable
Linux 64 bit snaphttps://update.code.visualstudio.com/{version}/linux-snap-x64/stable
Linux ARMhttps://update.code.visualstudio.com/{version}/linux-armhf/stable
Linux ARM debianhttps://update.code.visualstudio.com/{version}/linux-deb-armhf/stable
Linux ARM rpmhttps://update.code.visualstudio.com/{version}/linux-rpm-armhf/stable
Linux 64 bit ARMhttps://update.code.visualstudio.com/{version}/linux-arm64/stable
Linux 64 bit ARM debianhttps://update.code.visualstudio.com/{version}/linux-deb-arm64/stable
Linux 64 bit ARM rpmhttps://update.code.visualstudio.com/{version}/linux-rpm-arm64/stable

Substitute the specific release you want in the {version} placeholder. For example, to download the Linux ARM debian version for 1.50.1, you would use

You can use the version string latest, if you'd like to always download the latest VS Code stable version.

Prerelease versions

Want an early peek at new VS Code features? You can try prerelease versions of VS Code by installing the 'Insiders' build. The Insiders build installs side by side to your stable VS Code install and has isolated settings, configurations and extensions. The Insiders build is updated nightly so you'll get the latest bug fixes and feature updates from the day before.

To install the Insiders build, go to the Insiders download page.

What is a VS Code 'workspace'?

A VS Code 'workspace' is usually just your project root folder. VS Code uses the 'workspace' concept in order to scope project configurations such as project-specific settings as well as config files for debugging and tasks. Workspace files are stored at the project root in a .vscode folder. You can also have more than one root folder in a VS Code workspace through a feature called Multi-root workspaces.

Can I run a portable version of VS Code?

Yes, VS Code has a Portable Mode which lets you keep settings and data in the same location as your installation, for example, on a USB drive.

Report an issue with a VS Code extension

For bugs, feature requests or to contact an extension author, you should use the links available in the Visual Studio Code Marketplace or use Help: Report Issue from the Command Palette. However, if there is an issue where an extension does not follow our code of conduct, for example it includes profanity, pornography or presents a risk to the user, then we have an email alias to report the issue. Once the mail is received, our Marketplace team will look into an appropriate course of action, up to and including unpublishing the extension.

VS Code gets unresponsive right after opening a folder

When you open a folder, VS Code will search for typical project files to offer you additional tooling (e.g. the solution picker in the status bar to open a solution). If you open a folder with lots of files, the search can take a large amount of time and CPU resources during which VS Code might be slow to respond. We plan to improve this in the future but for now you can exclude folders from the explorer via the files.exclude setting and they will not be searched for project files:

VS Code is blank?

The Electron shell used by Visual Studio Code has trouble with some GPU (graphics processing unit) hardware acceleration. If VS Code is displaying a blank (empty) main window, you can try disabling GPU acceleration when launching VS Code by adding the Electron --disable-gpu command-line switch.

Installation appears to be corrupt [Unsupported]

VS Code does a background check to detect if the installation has been changed on disk and if so, you will see the text [Unsupported] in the title bar. This is done since some extensions directly modify (patch) the VS Code product in such a way that is semi-permanent (until the next update) and this can cause hard to reproduce issues. We are not trying to block VS Code patching, but we want to raise awareness that patching VS Code means you are running an unsupported version. Reinstalling VS Code will replace the modified files and silence the warning.

You may also see the [Unsupported] message if VS Code files have been mistakenly quarantined or removed by anti-virus software (see issue #94858 for an example). Check your anti-virus software settings and reinstall VS Code to repair the missing files.

Technical Support

You can ask questions and search for answers on Stack Overflow and enter issues and feature requests directly in our GitHub repository.

If you'd like to contact a professional support engineer, you can open a ticket with the Microsoft assisted support team.

-->

Python is a popular programming language that is reliable, flexible, easy to learn, free to use on all operating systems, and supported by both a strong developer community and many free libraries. Python supports all manners of development, including web applications, web services, desktop apps, scripting, and scientific computing, and is used by many universities, scientists, casual developers, and professional developers alike. You can learn more about the language on python.org and Python for Beginners.

Visual Studio is a powerful Python IDE on Windows. Visual Studio provides open-source support for the Python language through the Python Development and Data Science workloads (Visual Studio 2017 and later) and the free Python Tools for Visual Studio extension (Visual Studio 2015 and earlier).

Visual Studio For Mac And Linux Virtualbox

Python is not presently supported in Visual Studio for Mac, but is available on Mac and Linux through Visual Studio Code (see questions and answers).

To get started:

  • Follow the installation instructions to set up the Python workload.
  • Familiarize yourself with the Python capabilities of Visual Studio through the sections in this article.
  • Go through one or more of the Quickstarts to create a project. If you're unsure, start with Create a web app with Flask.
  • Go through one or more of the Quickstarts to create a project. If you're unsure, start with Quickstart: Open and run Python code in a folder or Create a web app with Flask.
  • Follow the Work with Python in Visual Studio tutorial for a full end-to-end experience.

Note

Visual Studio supports Python version 2.7, as well as version 3.5 through 3.7. While it is possible to use Visual Studio to edit code written in other versions of Python, those versions are not officially supported and features such as IntelliSense and debugging might not work. Python version 3.8 support is still under development, specific details about support can be seen in this tracking issue on GitHub.

Support for multiple interpreters

Visual Studio's Python Environments window (shown below in a wide, expanded view) gives you a single place to manage all of your global Python environments, conda environments, and virtual environments. Visual Studio automatically detects installations of Python in standard locations, and allows you to configure custom installations. With each environment, you can easily manage packages, open an interactive window for that environment, and access environment folders.

Use the Open interactive window command to run Python interactively within the context of Visual Studio. Use the Open in PowerShell command to open a separate command window in the folder of the selected environment. From that command window you can run any python script.

For more information:

Rich editing, IntelliSense, and code comprehension

Visual Studio provides a first-class Python editor, including syntax coloring, auto-complete across all your code and libraries, code formatting, signature help, refactoring, linting, and type hints. Visual Studio also provides unique features like class view, Go to Definition, Find All References, and code snippets. Direct integration with the Interactive window helps you quickly develop Python code that's already saved in a file.

For more information:

  • Docs: Edit Python code
  • Docs: Format code
  • Docs: Refactor code
  • Docs: Use a linter
  • General Visual Studio feature docs: Features of the code editor

Interactive window

For every Python environment known to Visual Studio, you can easily open the same interactive (REPL) environment for a Python interpreter directly within Visual Studio, rather than using a separate command prompt. You can easily switch between environments as well. (To open a separate command prompt, select your desired environment in the Python Environments window, then select the Open in PowerShell command as explained earlier under Support for multiple interpreters.)

Visual Studio also provides tight integration between the Python code editor and the Interactive window. The Ctrl+Enter keyboard shortcut conveniently sends the current line of code (or code block) in the editor to the Interactive window, then moves to the next line (or block). Ctrl+Enter lets you easily step through code without having to run the debugger. You can also send selected code to the Interactive window with the same keystroke, and easily paste code from the Interactive window into the editor. Together, these capabilities allow you to work out details for a segment of code in the Interactive window and easily save the results in a file in the editor.

Visual Studio also supports IPython/Jupyter in the REPL, including inline plots, .NET, and Windows Presentation Foundation (WPF).

For more information:

Project system, and project and item templates

Note

Visual Studio 2019 supports opening a folder containing Python code and running that code without creating Visual Studio project and solution files. For more information, see Quickstart: Open and run Python code in a folder. There are, however, benefits to using a project file, as explained in this section.

Visual Studio helps you manage the complexity of a project as it grows over time. A Visual Studio project is much more than a folder structure: it includes an understanding of how different files are used and how they relate to each other. Visual Studio helps you distinguish app code, test code, web pages, JavaScript, build scripts, and so on, which then enable file-appropriate features. A Visual Studio solution, moreover, helps you manage multiple related projects, such as a Python project and a C++ extension project.

Project and item templates automate the process of setting up different types of projects and files, saving you valuable time and relieving you from managing intricate and error-prone details. Visual Studio provides templates for web, Azure, data science, console, and other types of projects, along with templates for files like Python classes, unit tests, Azure web configuration, HTML, and even Django apps.

For more information:

  • Docs: Manage Python projects
  • Docs: Item templates reference
  • Docs: Python project templates
  • Docs: Work with C++ and Python
  • General Visual Studio feature docs: Project and item templates
  • General Visual Studio feature docs: Solutions and projects in Visual Studio

Visual Studio Professional For Mac

Full-featured debugging

One of Visual Studio's strengths is its powerful debugger. For Python in particular, Visual Studio includes Python/C++ mixed-mode debugging, remote debugging on Linux, debugging within the Interactive window, and debugging Python unit tests.

Click Install. Click Restart.If your installation fails, it will be likely due to macOS Security and Privacy settings. Ustream for mac. Click Continue. Enter your password.

In Visual Studio 2019, you can run and debug code without having a Visual Studio project file. See Quickstart: Open and run Python code in a folder for an example.

For more information:

  • Docs: Debug Python
  • Docs: Python/C++ mixed-mode debugging
  • Docs: Remote debugging on Linux
  • General Visual Studio feature docs: Feature tour of the Visual Studio Debugger

Profiling tools with comprehensive reporting

Profiling explores how time is being spent within your application. Visual Studio supports profiling with CPython-based interpreters and includes the ability to compare performance between different profiling runs.

For more information:

  • Docs: Python profiling tools
  • General Visual Studio feature docs: Profiling Feature Tour. (Not all Visual Studio profiling features are available for Python).

Visual Studio For Mac And Linux Operating System

Unit testing tools

Discover, run, and manage tests in Visual Studio Test Explorer, and easily debug unit tests.

For more information:

  • Docs: Unit testing tools for Python
  • General Visual Studio feature docs: Unit test your code.

Azure SDK for Python

The Azure libraries for Python simplify consuming Azure services from Windows, Mac OS X, and Linux apps. You can use them to create and manage Azure resources, as well as to connect to Azure services.

For more information, see Azure SDK for Python and Azure libraries for Python.

Questions and answers

Q. Is Python support available with Visual Studio for Mac?

A. Not at this time, but you can up vote the request on Developer Community. The Visual Studio for Mac documentation identifies the current types of development that it does support. In the meantime, Visual Studio Code on Windows, Mac, and Linux works well with Python through available extensions.

Q. What can I use to build UI with Python?

A. The main offering in this area is the Qt Project, with bindings for Python known as PySide (the official binding) (also see PySide downloads) and PyQt. At present, Python support in Visual Studio does not include any specific tools for UI development.

Q. Can a Python project produce a stand-alone executable?

A. Python is generally an interpreted language, with which code is run on demand in a suitable Python-capable environment such as Visual Studio and web servers. Visual Studio itself does not at present provide the means to create a stand-alone executable, which essentially means a program with an embedded Python interpreter. However, the Python community supplied different means to create executables as described on StackOverflow. CPython also supports being embedded within a native application, as described on the blog post, Using CPython's embeddable zip file.

Feature support

Python features can be installed in the following editions of Visual Studio as described in the installation guide:

  • Visual Studio 2017 (all editions)
  • Visual Studio 2015 (all editions)
  • Visual Studio 2013 Community Edition
  • Visual Studio 2013 Express for Web, Update 2 or higher
  • Visual Studio 2013 Express for Desktop, Update 2 or higher
  • Visual Studio 2013 (Pro edition or higher)
  • Visual Studio 2012 (Pro edition or higher)
  • Visual Studio 2010 SP1 (Pro edition or higher; .NET 4.5 required)

Visual Studio 2015 and earlier are available at visualstudio.microsoft.com/vs/older-downloads/.

Important

Features are fully supported and maintained for only the latest version of Visual Studio. Features are available in older versions but are not actively maintained.

Python support2017+20152013 Comm2013 Desktop2013 Web2013 Pro+2012 Pro+2010 SP1 Pro+
Manage multiple interpreters
Auto-detect popular interpreters
Add custom interpreters
Virtual Environments
Pip/Easy Install

Project system2017+20152013 Comm2013 Desktop2013 Web2013 Pro+2012 Pro+2010 SP1 Pro+
New project from existing code
Show all files
Source control
Git integration1

Editing2017+20152013 Comm2013 Desktop2013 Web2013 Pro+2012 Pro+2010 SP1 Pro+
Syntax highlighting
Auto-complete
Signature help
Quick info
Object browser/class view
Navigation bar
Go to Definition
Navigate to
Find All References
Auto indentation
Code formatting
Refactor - rename
Refactor - extract method
Refactor - add/remove import
PyLint

Interactive window2017+20152013 Comm2013 Desktop2013 Web2013 Pro+2012 Pro+2010 SP1 Pro+
Interactive window
IPython with inline graphs

Desktop2017+20152013 Comm2013 Desktop2013 Web2013 Pro+2012 Pro+2010 SP1 Pro+
Console/Windows application
IronPython WPF (with XAML designer)
IronPython Windows Forms

Web2017+20152013 Comm2013 Desktop2013 Web2013 Pro+2012 Pro+2010 SP1 Pro+
Django web project
Bottle web project
Flask web project
Generic web project

Azure2017+20152013 Comm2013 Desktop2013 Web2013 Pro+2012 Pro+2010 SP1 Pro+
Deploy to web site2
Deploy to web role443
Deploy to worker role???443
Run in Azure emulator???443
Remote debugging688
Attach Server Explorer77

Django templates2017+20152013 Comm2013 Desktop2013 Web2013 Pro+2012 Pro+2010 SP1 Pro+
Debugging
Auto-complete55
Auto-complete for CSS and JavaScript55

Debugging2017+20152013 Comm2013 Desktop2013 Web2013 Pro+2012 Pro+2010 SP1 Pro+
Debugging
Debugging without a project
Debugging - attach to editing
Mixed-mode debugging
Remote debugging (Windows, Mac OS X, Linux)
Debug Interactive window

Profiling2017+20152013 Comm2013 Desktop2013 Web2013 Pro+2012 Pro+2010 SP1 Pro+
Profiling

Test2017+20152013 Comm2013 Desktop2013 Web2013 Pro+2012 Pro+2010 SP1 Pro+
Test explorer
Run test
Debug test

  1. Git support for Visual Studio 2012 is available in the Visual Studio Tools for Git extension, available on the Visual Studio Marketplace.

  2. Deployment to Azure Web Site requires Azure SDK for .NET 2.1 - Visual Studio 2010 SP1. Later versions don't support Visual Studio 2010.

  3. Support for Azure Web Role and Worker Role requires Azure SDK for .NET 2.3 - VS 2012 or later.

  4. Support for Azure Web Role and Worker Role requires Azure SDK for .NET 2.3 - VS 2013 or later.

  5. Django template editor in Visual Studio 2013 has some known issues that are resolved by installing Update 2.

  6. Requires Windows 8 or later. Visual Studio 2013 Express for Web doesn't have the Attach to Process dialog, but Azure Web Site remote debugging is still possible using the Attach Debugger (Python) command in Server Explorer. Remote debugging requires Azure SDK for .NET 2.3 - Visual Studio 2013 or later.

  7. Requires Windows 8 or later. Attach Debugger (Python) command in Server Explorer requires Azure SDK for .NET 2.3 - Visual Studio 2013 or later.

  8. Requires Windows 8 or later.





broken image