MSBuild projects can be referenced in project.json as dependencies to add additional metadata such as include/exclude. The problem is that Visual Studio allows duplicate project names, to solve this NuGet creates unique names by adding the solution folders to the name.
Example: If a project MyProject is under a solution folder src it will be given the name src\\MyProject
This name isn't obvious to the users.
The name is also displayed in the lock file.
One possible solution is to use the project name until a conflict is hit, then all conflicts will be forced to use the full unique name.
NuGet could also support understanding both the unique and short name.
MSBuild projects can be referenced in project.json as dependencies to add additional metadata such as include/exclude. The problem is that Visual Studio allows duplicate project names, to solve this NuGet creates unique names by adding the solution folders to the name.
Example: If a project
MyProjectis under a solution foldersrcit will be given the namesrc\\MyProjectThis name isn't obvious to the users.
The name is also displayed in the lock file.
One possible solution is to use the project name until a conflict is hit, then all conflicts will be forced to use the full unique name.
NuGet could also support understanding both the unique and short name.