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

Consistently getting "Specify which project file to use..." #265

Open
threadz opened this issue Sep 18, 2019 · 5 comments
Open

Consistently getting "Specify which project file to use..." #265

threadz opened this issue Sep 18, 2019 · 5 comments

Comments

@threadz
Copy link

threadz commented Sep 18, 2019

After installing and attempting to run, I'm consistently getting...
"Specify which project file to use because this 'D:\ATLASSVN\Common\source\Utilities\Utilities' contains more than one project file."

My command line is: dotnet migrate-2019 wizard "Utilities.csproj"

The directory actually only contains one .csproj file. I've attached my .csproj file and a screenshot of my command window.

If there anything I'm obviously doing wrong?

Utilities.csproj.zip

2019-09-19 11_12_24-Common- Microsoft Visual Studio (Administrator)

@hvanbakel
Copy link
Owner

hvanbakel commented Sep 19, 2019 via email

@threadz
Copy link
Author

threadz commented Sep 19, 2019

No. Project file in the Utilities directory is called Utilities.csproj. I was referencing the project file directly from the command line.

It's a .NET Framework 4 class library.

Seemed a weird error message to me too.

@andrew-boyarshin
Copy link
Collaborator

@threadz It's strange, to the point of being weird.

  1. There is currently no such string in this project. It's not the message of dotnet-migrate-2019.

  2. Even if there were, the wizard should list all ambiguous variants (in case there are less than 5).

  3. What is your version of project2015to2017.migrate2019.tool (dotnet tool list -g)?

  4. Try turning on extreme log verbosity. dotnet migrate-2019 -v diag wizard "Utilities.csproj"

  5. Try specifying ".\Utilities.csproj" or full path. Try not specifying anything, it should pick that file, since it's the only project/solution file in the current working directory.

@threadz
Copy link
Author

threadz commented Sep 19, 2019

Wow, that is odd then. Here's the screenshot from the CMD window with your suggestions...

2019-09-19 15_03_03-C__WINDOWS_system32_cmd exe

@hvanbakel
Copy link
Owner

Apparently this error is also run when running dotnet ef
dotnet/efcore#11315

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

No branches or pull requests

3 participants