Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Migrating an sln with a xproj with different name results in the wrong csproj path in the sln

See original GitHub issue

Steps to reproduce

migrate and build https://github.com/aspnet/AzureIntegration

Expected behavior

build succeeded

Actual behavior

The project file "D:\aspnetsrc\AzureIntegration\test\Microsoft.AspNetCore.AzureAppServicesIntegration.Tests\Microsoft.AspNetCore.AzureAppServicesIntegration.Test.csproj" was not found. [D:\aspnetsrc\AzureIntegration\AzureIntegration.sln]

The name of csproj after migration does not have ‘s’ in ‘Tests’ - name should be coming from xproj name or some attribute inside - it is coming from folder name instead

Environment data

dotnet --info output:

.NET Command Line Tools (1.0.0-rc4)

Product Information:
 Version:            1.0.0-rc4
 Commit SHA-1 hash:  cf8fd7dd34

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.14393
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   D:\cli\artifacts\win10-x64\stage2\sdk\1.0.0-preview5-004506

Issue Analytics

State:
Created 7 years ago
Comments:10 (10 by maintainers)

Top GitHub Comments

2reactions

livarcocccommented, Jan 13, 2017

@DustinCampbell I agree. This means that the bug here is that migration is not putting the right csproj file name/path in the sln when it modifies it.

0reactions

livarcocccommented, Jan 13, 2017

Ok, closing this as a dup then.