Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VS Code through Windows Explorer integration doesn't function if there is another instance of VS Code already open #3180

Closed
trstringer opened this issue Feb 19, 2016 · 8 comments
Assignees
Labels
install-update VS Code installation and upgrade system issues

Comments

@trstringer
Copy link
Contributor

If you already have VS Code open (either with an open folder/file or an empty window), if you try to open up a second instance of VS Code by right-clicking on a file/folder in Windows Explorer and click Open with Code, nothing happens. The desired functionality would be for opening files/folders through Windows Explorer integration to function even if there are already opened instances of VS Code.

Repro Steps

  1. Open up VS Code (doesn't matter if you open up VS Code with no file or folder, the behavior is the same)
  2. In Windows Explorer, navigate to a folder with a flat file
  3. Right-click on the file and select Open with Code
  4. Note that this attempt at opening a 2nd instance of VS Code through Windows Explorer doesn't succeed
@egamma egamma assigned joaomoreno and unassigned bpasero Feb 20, 2016
@egamma egamma added the install-update VS Code installation and upgrade system issues label Feb 20, 2016
@joaomoreno joaomoreno assigned bpasero and unassigned joaomoreno Feb 22, 2016
@anandgupta08
Copy link

I am also experiencing the same problem. However i seem to have this issue in one machine, but not in another even though the both have the same VS Code version.

@Tyriar
Copy link
Member

Tyriar commented Feb 23, 2016

I think this is intentional behavior since Code doesn't launch two instances for the same folder. Related discussion #48

@trstringer
Copy link
Contributor Author

@Tyriar that isn't the behavior I'm seeing. You say for the same folder. The second instance launch attempt could/would be for a totally different folder. That's the problem. Folder1 is open in VSCode instance1, trying to open Folder2 for a 2nd VSCode instance from Windows Explorer fails.

@Tyriar Tyriar added the bug Issue identified by VS Code Team member as probable bug label Feb 24, 2016
@bpasero bpasero added this to the March 2016 milestone Feb 29, 2016
@bpasero
Copy link
Member

bpasero commented Feb 29, 2016

@tstringer Windows 10?

@trstringer
Copy link
Contributor Author

@bpasero That's correct, Windows 10.

@bpasero
Copy link
Member

bpasero commented Mar 1, 2016

very likely #929

@bpasero bpasero closed this as completed Mar 1, 2016
@bpasero bpasero removed the bug Issue identified by VS Code Team member as probable bug label Mar 14, 2016
@bpasero bpasero modified the milestone: March 2016 Mar 23, 2016
@DanTup
Copy link
Contributor

DanTup commented Jul 30, 2016

@bpasero I don't believe this is #929.

I'm on Windows 10 and have Code open for a folder (M:\Coding\Applications\Dart-Code) and I'm double-clicking on a Markdown file M:\Apps\Dart\lib\analysis_server\README.md and nothing is happening. If I manually switch to the Code window I have open, the README has most certainly not opened.

(It's not isolated to this time, I've never been able to open a second instance, not even by clicking the "New Window" task under VS Code from the Taskbar, or middle-clicking on it!)

@DanTup
Copy link
Contributor

DanTup commented Jul 30, 2016

Ok, figured this out - it happens when the instance of Code already open is elevated - I launched it from an Admin PoSh window. If I open it as non-Admin then I don't see this behaviour.

It definitely doesn't make sense to behave like this; let me know if I should open a new issue or you'll just reuse this one.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
install-update VS Code installation and upgrade system issues
Projects
None yet
Development

No branches or pull requests

7 participants