https://bugs.winehq.org/show_bug.cgi?id=48337
--- Comment #4 from Alexandre Julliard julliard@winehq.org --- (In reply to Artem S. Tashkinov from comment #3)
(In reply to Alexandre Julliard from comment #2)
That wouldn't help you, because it only affects the search order for the dll file. Once the file is found it would still be subject to the native/builtin configuration, since that's not based on the search path.
In that case we should assume that the user requested "native, builtin" 'cause it's how Windows operates.
This doesn't make sense, there's no native/builtin distinction in Windows. And there's nothing special about .local, it's an alternative to using a manifest or putting dlls in the app directory, having it behave differently would be weird.
Please implement this feature as I believe it's quite easy and simple to program and it's a lot more easier to use than using winecfg or creating registry files with overrides (both of which are cumbersome).
It's not as easy as you think.