From: Steve Harter Date: Fri, 9 Feb 2018 00:34:47 +0000 (-0600) Subject: Update assembly-conflict-resolution.md X-Git-Tag: submit/tizen/20210909.063632~11032^2~889 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=3e8e7f7ddf98830e6efdf2b2e5edfc8760ad570d;p=platform%2Fupstream%2Fdotnet%2Fruntime.git Update assembly-conflict-resolution.md Commit migrated from https://github.com/dotnet/core-setup/commit/17401eeda3880d657a8949895ca90f7e8392cfd3 --- diff --git a/docs/installer/design-docs/assembly-conflict-resolution.md b/docs/installer/design-docs/assembly-conflict-resolution.md index 5234a08..f629b2a 100644 --- a/docs/installer/design-docs/assembly-conflict-resolution.md +++ b/docs/installer/design-docs/assembly-conflict-resolution.md @@ -57,6 +57,6 @@ Probe the app location before the framework's. This means flip (3) and (4) under Replace step 5 under **Algorithm** above with: * If the probing path is a framework, and no [minor] or [major] roll-forward occurred on that framework, then check its deps.json to see if it contains the exact package (by name and version). If so, then use the framework's location -* If the probing path is a framework, and a [minor] or [major] roll-forward occurred on that framework, then check its deps.json to see if it contains a newer version of the assembly (by File Version and \ or Assembly Version). If so, then use the framework's location +* If the probing path is a framework, and a [minor] or [major] roll-forward occurred on that framework, then check its deps.json to see if it contains a newer version of the assembly (by Assembly Version and then File Version if necessary). If so, then use the framework's location -In order to compare File Version and \ Assembly Version, additional metadata will need to be written to each deps.json file. If this metadata is not present (as in the case of applications published prior to 2.1) then the files will be considered older and will not replace any previously found locations. +In order to compare Assembly Version and File Version, additional metadata will need to be written to each deps.json file. If this metadata is not present (as in the case of applications published prior to 2.1) then the files will be considered older and will not replace any previously found locations.