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

Restore option is getting displayed for both project.json file and csproj file. #1233

Closed
anuraj opened this issue Feb 13, 2017 · 4 comments
Closed

Comments

@anuraj
Copy link

anuraj commented Feb 13, 2017

Environment data

dotnet --info output:
.NET Command Line Tools (1.0.0-preview4-004233)

Product Information:
Version: 1.0.0-preview4-004233
Commit SHA-1 hash: 8cec61c6f7

Runtime Environment:
OS Name: Windows
OS Version: 10.0.14393
OS Platform: Windows
RID: win10-x64
Base Path: C:\Program Files\dotnet\sdk\1.0.0-preview4-004233

VS Code version:Version 1.9.1
C# Extension version:1.7.0

Steps to reproduce

  1. Migrated my existing dotnet core project using dotnet migrate command, which created backup folder and moved project.json file inside it.
  2. Then open the project folder in VSCode.
  3. Here is the screenshot.

image

Expected behavior

Only one restore prompt should come, from the selected project file.

Actual behavior

Two prompts are coming to restore

@DustinCampbell
Copy link
Member

We still support project.json in VS Code and it's entirely possible that you might use VS Code with partially-converted code base. So, it's actually pretty tricky to determine whether project.json files should be restored or not (and not break something else). This isn't a great experience, but it's sort of working as designed.

@steelwil
Copy link

steelwil commented Apr 5, 2017

Is there a configuration setting that can set somewhere? I am using VS Code but I still need to support VS2015.

@DustinCampbell
Copy link
Member

If you want to disable processing of project.json projects, you can add an omnisharp.json file to your root folder with the following content:

{
    "dotnet": {
        "enabled": false
    }
}

@rchande
Copy link

rchande commented Jun 13, 2018

Looks like there's a workaround for this problem. Closing the issue--feel free to open a new one if you're still having problems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants