Re: Allow loading of built-in dlls with LOAD_LIBRARY_AS_DATAFILE flag set

[Alexandre Julliard]

"Dmitry Timoshkov" <dmitry(a)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.

-- 
Alexandre Julliard
julliard(a)winehq.com

Allow loading of built-in dlls with LOAD_LIBRARY_AS_DATAFILE flag set

[Dmitry Timoshkov]

"Alexandre Julliard" <julliard(a)winehq.com> wrote:
> 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.

Perhaps version.dll code should use DONT_RESOLVE_DLL_REFERENCES instead of
undesirable LOAD_LIBRARY_AS_DATAFILE?

Will DONT_RESOLVE_DLL_REFERENCES work with built-in dlls somewhere in the future?