Allow missing assembly dependencies for components. (dotnet/core-setup#4751)
authorVitek Karas <vitek.karas@microsoft.com>
Wed, 14 Nov 2018 11:15:30 +0000 (03:15 -0800)
committerGitHub <noreply@github.com>
Wed, 14 Nov 2018 11:15:30 +0000 (03:15 -0800)
commit17c61880ae0d5ef1c2b1df3a9b8aa0c9660dab4d
tree31309793278881bc7109176a8e46b36621021dd6
parent5bcb8c5c57aba5a229d2b56d6cb963db7cf43453
Allow missing assembly dependencies for components. (dotnet/core-setup#4751)

When resolving assembly dependencies for components, don't fail if the assembly doesn't exist on the disk (but it's still present in the .deps.json as a runtime asset).
For dynamically loaded components this behavior makes sense as such components are typically distributed as just the necessary pieces, with everything else provided by the app.

This is a temporary change mainly as a workaround for dotnet/sdkdotnet/core-setup#2660. Issue dotnet/core-setupdotnet/core-setup#4752 is tracking future need for revisiting this change.

Commit migrated from https://github.com/dotnet/core-setup/commit/ca431d0cefee116b5c4ca292961ab60ddd81611f
src/installer/corehost/cli/deps_resolver.cpp
src/installer/corehost/cli/deps_resolver.h
src/installer/corehost/cli/hostpolicy.cpp
src/installer/test/HostActivationTests/GivenThatICareAboutComponentDependencyResolution.cs