On Sat, Oct 17, 2009 at 6:31 AM, Jeremy White jwhite@codeweavers.com wrote:
Alexandre wanted a version check when asked a different question. That question was when would we prefer an available native Richedit over the builtin one. (i.e. in the LoadLibrary("riched20") case).
Looking back at the bug, that one uses an absolute path, too: 00e6:Call KERNEL32.LoadLibraryA(0032a40c "C:\Program Files\Common Files\Microsoft Shared\office12\riched20.dll") ret=3261c0d6
I think if we get a loadlibrary on an explicit private path, we should load that dll natively, even if we have a builtin dll of the same name.
Totally. - Dan