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

Specify which project file to use when inside project directory #11315

Closed
thealmogg opened this issue Mar 17, 2018 · 4 comments
Closed

Specify which project file to use when inside project directory #11315

thealmogg opened this issue Mar 17, 2018 · 4 comments
Labels
closed-no-further-action The issue is closed and no further action is planned. customer-reported

Comments

@thealmogg
Copy link

thealmogg commented Mar 17, 2018

Hi,
Trying to use "dotnet ef" command in Package Manager Console.
the PMC is cd to the .csproj directory, and still getting:
dotnet : Specify which project file to use because this 'C:\Users\PC-NAME\Source\Repos\TestProject\Test" contains more than one project file.
At line:1 char:1

  • dotnet ef migrations add TestMigration
  •   + CategoryInfo          : NotSpecified: (Specify which p...e project file.:String) [], RemoteException
      + FullyQualifiedErrorId : NativeCommandError
    
    

Tried use -p / --p and point to the .csproj file / directory - still same error.
Using .NET CORE, MVC project, Latest EF Core 2.0.2 version.

@bricelam
Copy link
Contributor

Answered on Stack Overflow.

@bricelam bricelam added closed-no-further-action The issue is closed and no further action is planned. and removed type-investigation labels Mar 19, 2018
@bricelam bricelam removed their assignment Mar 19, 2018
@bricelam bricelam removed this from the 2.1.0 milestone Mar 19, 2018
@letto4135
Copy link

Answered on Stack Overflow.

Your answer was bad and you should feel bad.

@brenocg1
Copy link

brenocg1 commented Apr 6, 2021

Didn't work :(

@bricelam
Copy link
Contributor

bricelam commented May 5, 2021

I think you guys are looking for #21655 (comment)

@ajcvickers ajcvickers reopened this Oct 16, 2022
@ajcvickers ajcvickers closed this as not planned Won't fix, can't repro, duplicate, stale Oct 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed-no-further-action The issue is closed and no further action is planned. customer-reported
Projects
None yet
Development

No branches or pull requests

5 participants