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

Migrate does not understand transitive project references that have already been migrated. #7075

Closed
NTaylorMullen opened this issue Nov 2, 2016 · 1 comment

Comments

@NTaylorMullen
Copy link
Contributor

Steps to reproduce

  • Unzip TransitiveMigrationRepro.zip. Project3 has already been migrated and the graph is Project1 => Project2 => Project3.
  • cd src/Project1 (can also go into Project2)
  • dotnet migrate

Expected behavior

  • Migration succeeds

Actual behavior

Could not find file 'C:\Users\nimullen\Documents\temp\bug\src\Project3\project.json'.
Migration failed.

Note: Project2/project.json does exist.

Environment data

dotnet --info output:

.NET Command Line Tools (1.0.0-preview3-004007)

Product Information:
 Version:            1.0.0-preview3-004007
 Commit SHA-1 hash:  80ec02b4da

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.14393
 OS Platform: Windows
 RID:         win10-x64

/cc @livarcocc

@livarcocc
Copy link
Contributor

This means that we didn't have enough context to know what project3 was needed, it migrated successfully and it was then moved to backup. After that, we can't find a project.json for it when migrating project1 and migration fails.

If you want to run migration like that, you can pass the --no-backup to dotnet migrate and we won't move files around.

@msftgits msftgits transferred this issue from dotnet/cli Jan 31, 2020
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

2 participants