Skip to content
Tutorials Center
My learning

Topics

Lesson 5 of 40 ยท Getting Started

VS Code, Visual Studio and vscode.dev

Sort out the Visual Studio family: how VS Code differs from Visual Studio, what Codespaces and vscode.dev are, and how Stable, Insiders and portable builds fit together.

The names around VS Code confuse many newcomers. "Visual Studio" and "Visual Studio Code" sound alike but are different products. There is also a version that runs in a browser tab, an Insiders channel and a portable mode. This lesson draws the map so you pick the right tool and the right edition.

Visual Studio versus Visual Studio Code

Visual Studio Code Visual Studio
Kind Extensible editor Full IDE
Platforms Windows, macOS, Linux, browser Windows (a separate older Mac product was retired)
Cost Free Community edition free for individuals and small teams; Professional and Enterprise paid
Size and startup Light, fast Heavy, many GB with workloads
Strength Any language, web, scripting, remote work .NET, C++, Windows desktop, Unity, enterprise tooling
Project model Folders Solutions and projects (.sln, .csproj)

They share a name and some ideas, such as IntelliSense and a debugger UI, but they are different programs with different codebases. A good rule of thumb: for a large .NET or Windows C++ application with designers, profilers and project templates, Visual Studio is the more complete tool. For almost everything else, and for mixed-language work, VS Code is lighter and more flexible. Many .NET developers use both.

Stable and Insiders

  • Stable is released roughly monthly. Each release has release notes at Help > Release Notes.
  • Insiders is built every night from the latest development branch. It has its own icon (green), its own settings folder and its own extension set, and it installs next to Stable.

Use Insiders only if you want to try features before release or report bugs. Do not use it for your only working environment during a deadline.

Portable mode

On Windows and Linux you can run VS Code from a USB drive or a shared folder. Download the ZIP/tarball build, create a folder named data next to the executable, and VS Code stores settings and extensions in it instead of your user profile. Move the folder and your whole setup moves with it. This is useful on locked-down machines where you cannot install software.

Running VS Code in the browser

There are three ways to get VS Code in a web page.

vscode.dev is a lightweight editor that runs entirely in your browser. You can open local folders through the browser's file access feature (in browsers that support it), or open a GitHub repository directly. Extensions that only need a browser sandbox work; anything that needs a Node process or a native program does not run. There is no terminal that talks to your machine.

github.dev opens a repository in the same browser editor. On any GitHub repository press the . (dot) key, or change github.com to github.dev in the address bar. It is great for reading code and making a quick change and commit from a phone or a borrowed computer.

GitHub Codespaces starts a full cloud development container with a real terminal and runtime, and you use VS Code in the browser or connect from the desktop app. It supports running tests, servers and debugging, so it is the cloud option for real work. Codespaces is a paid service with a free monthly allowance for personal accounts.

flowchart TD
  A[Need VS Code?] --> B{Need to run code?}
  B -- No, just read or edit --> C[vscode.dev or github.dev]
  B -- Yes --> D{Where should it run?}
  D -- On my computer --> E[Desktop VS Code]
  D -- In the cloud --> F[Codespaces]
  D -- On another machine --> G[Remote SSH or Containers]

A decision path for choosing between the desktop app, browser editors and cloud environments.

  • Code - OSS is the open-source repository that Microsoft's build comes from. Some Linux distributions package it, and forks such as VSCodium remove Microsoft branding and use a different extension registry.
  • Visual Studio for Mac was retired; for .NET on macOS use VS Code with the C# Dev Kit.
  • Cursor, Windsurf and other AI editors are separate products built on the same open-source base. Most VS Code settings and many extensions carry over, but they are not VS Code.

A stand-in: choosing an environment

The decision path above is easy to turn into code. This JavaScript model is not a real recommendation engine; it just makes the reasoning explicit so you can try different situations.

JS Stand-in: which edition fits?

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Which edition should you install?

For this course, install Stable on your desktop. It gives you the full feature set, the integrated terminal and every extension. Treat the browser editors as convenient extras, and learn the remote options in Git and Remote Development when you reach that chapter.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. How is Visual Studio Code different from Visual Studio?

    They are different products: VS Code is cross-platform and extensible, while Visual Studio is a heavier full IDE.
  2. 2. What does pressing the . key on a GitHub repository page do?

    The dot key opens the repository in the web-based VS Code editor at github.dev.
  3. 3. Which option gives you a real terminal and runtime in the cloud?

    Codespaces runs a full development container; the browser-only editors cannot run your code.
  4. 4. How does portable mode keep your settings with the program?

    A folder named data beside the executable makes VS Code store settings and extensions there.

Summary

  • Visual Studio is a full IDE; Visual Studio Code is a light, cross-platform, extensible editor.
  • Stable is monthly; Insiders is nightly and installs alongside it.
  • Portable mode keeps everything in a data folder.
  • vscode.dev and github.dev are browser editors for reading and light editing; Codespaces is a full cloud environment.
  • For this course use the desktop Stable build.

Next: The Workbench Layout