Consider postponing reading and parsing of .deps.json in AssemblyDependencyResolver

[vitek-karas]

Currently AssemblyDependencyResolver does all the work in its constructor and caches the results for later use. Consider doing this lazily by storing the path to the assembly and only process its .deps.json when there's a first query on its contents.

To keep decent usability we should probably check the assembly path for existence in the .ctor and throw if it doesn't exist. But all the other failure modes would move from the constructor to the first usage.

[ghost]

Tagging subscribers to this area: @vitek-karas, @agocke, @VSadov
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Currently AssemblyDependencyResolver does all the work in its constructor and caches the results for later use. Consider doing this lazily by storing the path to the assembly and only process its .deps.json when there's a first query on its contents.

To keep decent usability we should probably check the assembly path for existence in the .ctor and throw if it doesn't exist. But all the other failure modes would move from the constructor to the first usage.

Author:	vitek-karas
Assignees:	-
Labels:	area-Host
Milestone:	Future