Great if icu-dotnet can use Windows-supplied icu dlls.

Summary

Recent Windows 10 (since version 1703) come with ICU4C, in particular icuuc.dll, icuin.dll, and icudt.dll, as documented here. It's great if icu-dotnet can use them, as an option or at least when no icu dlls are provided in the folder where icu.net.dll is in.

Is your feature request related to a problem? Please describe.

I wrote several small tools using icu-dotnet and felt that the installation footprint of several MB (even when using Icu4c.Win.Min binaries) is too large when compared to the main parts of my tools (less than 50KB each)...

Describe the solution you'd like

icu-dotnet to search the icu dlls in Windows' system32 folder when it is running on Windows and doesn't find ones in the standard folders (in the current version).

Describe alternatives you've considered

• icu-dotnet to provide a config option to only look for Windows' version of icu dlls,
• a separate version of icu-dotnet dedicated for Windows that always use Windows' version of icu dlls, and
• a version of icu4c.Win.Min and/or icu4c.Win.Full.Bin containing dlls that internally pass through to Windows' version of the icu dlls.

Additional context

The ICU version that Windows bundles is controlled only by Microsoft, so I think it is a good idea that icu-dotnet can use application-provided icu dlls of a particular version. Use of Windows' version of icu is for programs that are not sensitive to ICU (primarily data) version differences.

Start by locating the ICU DLL search and loading logic, then review how the wrapper currently finds application-provided ICU4C binaries on Windows. Add the requested fallback to Windows' system32 ICU DLLs when standard folders do not contain them, while preserving application-provided binaries; verify behavior on a supported Windows 10 system.