wine users - Sep 2011 - Locally "installed" Dll's

Some small utilities that I sometimes run are often distributed as a .ZIP file
containing the application and any DLL's that it depends on.

Windows has a behavior where if a DLL is located in the same directory as an
application, windows preferentially chooses the DLL's in that directory over
the same DLL that appears in C:\Windows\system32

Wine doesn't seem to behave this way (at least not version 1.3.28).  Is that
a correct assessment?  If so, is there a rationale for why wine doesn't
behave this way?  And would it be difficult to implement?  Or is there a setting
to enable this type of behavior?

In my current case, I'd hate to have to install vcrun2008 in a perfectly
good WINEPREFIX just to run one tiny application that came with its own dlls in
its local directory.

Thanks.

ischou wrote:
> Wine doesn't seem to behave this way (at least not version 1.3.28).  Is
that a correct assessment?  If so, is there a rationale for why wine doesn't
behave this way?
You are correct. If Wine's dll isn't compiled to prefer native Wine will
always try it's own first. This is intentional.


ischou wrote:
> And would it be difficult to implement?  Or is there a setting to enable
this type of behavior?
It's already implemented. Add your program to winecfg applications (first
tab). Select it, go to libraries tab, add whatever dlls you want it to use as
native, and set them to "native" or "native, builtin" order.


ischou wrote:
> In my current case, I'd hate to have to install vcrun2008 in a
perfectly good WINEPREFIX just to run one tiny application that came with its
own dlls in its local directory.
Newer (msvc7.0+) runtimes are special. They use manifest files, and won't
work if not properly installed, or manifests are missing...

ischou wrote:
> Is there something special I need to do to tell wine to use this manifest
file for this application?
Try putting manifest and whatever msvc runtime dll(s) you need into the
program's directory.