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

Settings open Visual Studio 2017 #1586

Closed
StefanFriptu opened this issue Jun 25, 2019 · 4 comments
Closed

Settings open Visual Studio 2017 #1586

StefanFriptu opened this issue Jun 25, 2019 · 4 comments
Labels
Resolution-By-Design It's supposed to be this way. Sometimes for compatibility reasons. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@StefanFriptu
Copy link

Environment

Windows build number: winnt 10.0.18362 on x86_64
Windows Terminal version (if applicable): 0.2.1715.0

Any other software? Visual Studio 2017

Steps to reproduce

  1. open windows terminal
  2. click on arrow down near the plus button -> settings or directly click ctrl + ,
  3. Visual Studio 2017 pops up

Expected behavior

I would expect to see a settings menu, definitely not vs2017

Actual behavior

vs2017 popus up

@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Jun 25, 2019
@Shorotshishir
Copy link

Shorotshishir commented Jun 25, 2019

perhaps In your Computer the Default application for opening .json files is VS2017, thus it is popping up. Try changing the default for .json to a text editor.

Refer to #1460

@dxk3355
Copy link

dxk3355 commented Jun 25, 2019

perhaps In your Computer the Default application for opening .json files is VS2017, thus it is popping up. Try changing the default for .json to a text editor.

Refer to #1460

Having a .json file for settings is not really user friendly, this is a Windows tool not Linux.

@DHowett-MSFT
Copy link
Contributor

DHowett-MSFT commented Jun 25, 2019

@dxk3355 /dup #1564

Others: this is currently by design. Get a better JSON editor if you don’t want it to launch VS.

@DHowett-MSFT DHowett-MSFT added the Resolution-By-Design It's supposed to be this way. Sometimes for compatibility reasons. label Jun 25, 2019
@ghost
Copy link

ghost commented Oct 21, 2020

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Oct 21, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution-By-Design It's supposed to be this way. Sometimes for compatibility reasons. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

4 participants