Skip to content
This repository has been archived by the owner on Apr 11, 2020. It is now read-only.

changes in global,json aren't reflected in solution explorer #2

Closed
lucamorelli opened this issue Mar 5, 2015 · 3 comments
Closed

Comments

@lucamorelli
Copy link

if I add directories in the source section of the global.json and save the file, the projects aren't added to the solution untile a kpm restore isn't triggeded.
Removing the source folder from the global.json the projects continues to be shown in the solution explorer, although I trigger the restore changing the project.json or even closing and reopening the solution.

@lucamorelli
Copy link
Author

I seen the first time a save the solution after the projects are added to the solution, those projects are added to the solution, and if I try to remove one of them and reload the project, until the source directory is present in the project.json the projects are readded to the solution, so pratically in this scenario is pratically unuseful to remove them.
Looks like If I remove the source directories from global.json and leave the projects in the solution they're unuseful, because k runtime are not treating them as source packages anymore, and if I used this way to add asp.net source packages to the solution, in the we application looks like those for thos packages the nuget version is used, not the source, looking at the icons in the solution explorer

@BillHiebert
Copy link

Thanks Luca. Yes this is a known issue and we have work items on our backlog to improve the experience.

@sayedihashimi
Copy link
Contributor

@lucamorelli here is what I tried with VS2015 RC.

  1. Create a new ASP.NET 5 web project
  2. Add a reference in project.json to an existing project on disk in another location
  3. Observe restored failed in solution explorer for the reference
  4. Modify global.json to include the folder that contains the other project

At that point the dependent project was added to the solution. I think we've fixed this, so I'll close this. Can you retry and reopen if you have issues?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants