search

dotnet / cli-migrate

MIT License
9 stars 15 forks source link

Migrating via VS 2017 (latest) references projects from the backup folder #15

Open livarcocc opened 7 years ago

livarcocc commented 7 years ago

From @christianhuening on March 24, 2017 14:1

Steps to reproduce

I tried to migrate a larger solution (57 projects) with VS 2017 and encountered some referencing issues. When investigating the non-resolvable references, I found that these references are pointing to the Backup folder created by the migration process. When manually re-adding the reference to that project from the actual solution, everything is fine again: d918482a-106b-11e7-9a36-ecfdba8e7037

Expected behavior

All project dependencies are linked to the actual projects.

Actual behavior

Some referenced projects were referenced to the Backup folder

Environment data

dotnet --info output: .NET Command Line Tools (1.0.1)

Product Information: Version: 1.0.1 Commit SHA-1 hash: 005db40cd1

Runtime Environment: OS Name: Mac OS X OS Version: 10.12 OS Platform: Darwin RID: osx.10.12-x64 Base Path: /usr/local/share/dotnet/sdk/1.0.1

Copied from original issue: dotnet/cli#6142

livarcocc commented 7 years ago

From @wilhen01 on April 26, 2017 10:58

I've just seen this on VS2017 Professional on Windows 10 migrating a DotNet Core VS2015 project.

livarcocc commented 7 years ago

From @jstallm on April 28, 2017 17:35

Noticed this same issue on 20 + project solution using VS2017 15.1 26403.7. After running dotnet migrate {solutionName}.sln it successfully creates the csproj files, but incorrectly forces the new .csproj files to reference backup folder for all references

livarcocc commented 7 years ago

From @jstallm on April 28, 2017 18:28

Solution for me was to simply remove every backup folder that was created, update global.json in solution version as shown below, then run dotnet migrate again. zzzzz