8000 Migrating via VS 2017 (latest) references projects from the backup folder · Issue #8000 · dotnet/sdk · GitHub
[go: up one dir, main page]

Skip to content
Migrating via VS 2017 (latest) references projects from the backup folder #8000
@christianhuening

Description

@christianhuening

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: 005db40

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0