mirrors/dotnet-installer
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

Fixes issue #781 makes CommandResolver comply with new implementation of --depsFile

Browse source
This commit is contained in:
piotrp 2016-01-11 00:14:14 -08:00
parent 6803bfd1ac
commit c5ce2eb753
7 changed files with 49 additions and 12 deletions
Download patch file Download diff file Expand all files Collapse all files

2
Documentation/specs/corehost.md
View file

@ -78,6 +78,8 @@ During host start-up, the host identifies if a `.deps` file is present and loads
A `.deps` file is **not** required to successfully launch an application, but without it, all the dependent assemblies must be located within the same folder as the application. Also, since servicing is performed on the basis of packages, an application without a `.deps` file cannot use the servicing index to override the location of assemblies.
The host looks for the `.deps` file in the Application Base with the file name `[AssemblyName].deps`. The path to the deps file can be overriden by specifying `--corehost-depsfile:{path to deps file}` as the first parameter to the application.
Given the set of assembly names, the host performs the following resolution. In some steps, the Package ID/Version/Relative Path data is required. This is only available if the assembly was listed in the deps file. If the assembly comes from the app-local folder, these resolution steps are skipped.
1. If there is an entry in the servicing index for the Package ID/Version/Relative Path associated with the assembly, the Servicing Root is concatenated with the New Asset Path from the index and used as the Assembly Path. This occurs **even if the assembly is also located app-local**, as long as it is also in the `.deps` file.