Wsrtjtyk

Use

code -n

when launching the program. This "Opens a new session of VS Code instead of restoring the previous session." (from here)

The way I used this was by modifying my "Code" shortcut to include the -n parameter:

If you want to open multiple instances of the same folder, then it is not currently supported. Watch and upvote this github issue if you want to see it implemented. https://github.com/Microsoft/vscode/issues/2686

Select File -> New Window from the menu and then open the other folder in the new window.

You can also create a shortcut with an empty filename

"%LOCALAPPDATA%LocalCodeCode.exe" ""

I like opening Visual Studio Code from run prompt/dialog instead. Sweet and simple cmd /c code -n. Since run dialog also maintains your command history on a per user basis so it is very convenient. One click and go -

Multiple instances of the same project

WORKAROUND

You cannot open multiple instances of the same folder but a workaround I have found is to open different folders.

lib

-components

-models

-helpers

tests

So, here I might open components, models and tests in different windows and then I can view them on my three monitors.

It sounds a bit simple but this has helped me a lot.

Starting with our 0.9.0 release, we added a new setting window.reopenFolders to control if VS Code should restore all folders of the previous session. By default only the last active window you worked on will be restored but if you change this setting to all, VS Code will reopen all folders in their windows automatically.

If you have all your JS files in multiple folders under one folder that works out very well, that's what i did:

To open a new instance with your project loaded from terminal, just type code <directory-path>

In Linux [Tested with Ubuntu & Kali] you can also right click the tile on the dock and select new window.

You can open multiple windows (from the menu or by running the code executable again).

However, unfortunately there seems to be no way to actually have separate instances a the moment. For example, if you have two shells open with different environments in each (different paths etc.), launching code for both will result in the second window sharing the same paths as the first, and ignoring the environment it was launched from.

Multiple VS Code windows can be opened on the same effective folder if each opens the folder through a different path. For example, on Windows, a project in C:GitMyProject could be open in one instance of VS Code, while MyPCc$GitMyProject is open in another instance. If the admin share (c$) isn't available or suitable, an explicit share can be constructed that provides the necessary access.

No, this isn't an ideal solution.