Hosting policy on casing resolution is different between Linux-Mac #42334
Comments
|
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
Dotnet-GitSync-Bot
added
the
untriaged
|
Tagging subscribers to this area: @vitek-karas, @agocke |
LakshanF
added a commit
to LakshanF/runtime
that referenced
this issue
Sep 16, 2020
Filed dotnet#42334 to track the linux-mac differences
jeffschwMSFT
removed
the
untriaged
LakshanF
added a commit
that referenced
this issue
Sep 17, 2020
* Harden AssemblyDependencyResolver assemblyPaths AssemblyDependencyResolver is made resilience to the case where hostpolicy.dll returns the same assembly paths by ignoring multiple entries. This is done by using OrdinalIgnoreCase comparison on Windows and Ordinal comparison elsewhere Fix #37162 * Pick the first simple assembly for multiples AssemblyDependencyResolver is made resilience to the case when hostpolicy.dll returns multiple assembly paths for the same assembly by picking the first one. Fix #37162 * missed an extra line * Test case for casing change with the same assembly * typo * Disabled the tests for non-windows Filed #42334 to track the linux-mac differences Co-authored-by: Lakshan Fernando <[email protected]>
macOS has case-insensitive file system by default. https://www.bing.com/search?q=macOS%20case%20insensitive%20file%20system |
LakshanF
added a commit
to LakshanF/runtime
that referenced
this issue
Sep 30, 2020
Merged
LakshanF
added a commit
that referenced
this issue
Sep 30, 2020
ghost
locked as resolved and limited conversation to collaborators
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
Changing the casing on an App assembly has different behavior in Linux & Mac in that deleting the .deps.json file and changing the case of the App assembly (ex. App.dll to app.dll) causes the app to fail in Linux and to pass in Mac (ex. run App.exe)
Given the underlying OS behavior for case comparison is similar in both, investigate this difference further and adjust the below test cases accordingly.
The following 3 tests in src\installer\tests\HostActivation.Tests\DependencyResolution\ResolveComponentDependencies.cs tracks the scenarios for all platforms. Do note that these tests are currently disable in non-windows platforms until this issues is investigated
Configuration
Regression?
No
The text was updated successfully, but these errors were encountered: