"Dmitry Timoshkov" dmitry@sloboda.ru writes:
But here is a problem. This doesn't honor a load order. If load order of a requested dll explicitly specified as 'builin' but 'native' library there is somewhere in the path, then we will get unexpected result. How to cope with it?
I think it's reasonable to give the native dll priority when doing LOAD_LIBRARY_AS_DATAFILE. An app using this wants to poke inside the dll binary file and we are much better off giving it the 'real' thing in this case IMO.