You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 18, 2017. It is now read-only.
Today, each element in projects of global.json should be a parent folder of your projects.
For example, you have src/WebApplication5/project.json , then src should be added to projects , instead of src/WebApplication5. If you add src/WebApplication5 as an element in global.json, we are unable to resolve it.
However, it's actually quite intuitive that I should be able to add src/MyProject to projects in global.json (based on name of the property).
As @davidfowl suggests, we should measure the performance hit before doing it.
The text was updated successfully, but these errors were encountered:
@glen-84 , thanks, I see your point. Yeah, with this change merged in, you will be able to add a specific project into global.json, without adding its peers.
Today, each element in projects of
global.json
should be a parent folder of your projects.For example, you have
src/WebApplication5/project.json
, thensrc
should be added to projects , instead ofsrc/WebApplication5
. If you addsrc/WebApplication5
as an element inglobal.json
, we are unable to resolve it.However, it's actually quite intuitive that I should be able to add
src/MyProject
toprojects
inglobal.json
(based on name of the property).As @davidfowl suggests, we should measure the performance hit before doing it.
The text was updated successfully, but these errors were encountered: