In reference to bug #11973, I've the following observation.
Using the native .NET 2.0 installed via winetricks, I located what is
potentially a problem with the method that .NET is using to locate the DLLs
that it wishes to load.
The problem seems to be that .NET is attempting to locate the
Am Mittwoch, 16. April 2008 16:43:13 schrieb Rhys McGuckin:
There are two possible ways currently that I can think of, which would
potentially solve this problem: 1. Have symbolic links within the system
directory (I find this to be bad method, for multiple reasons) 2. Have some
interception
Stefan Dösinger [EMAIL PROTECTED] wrote:Many applications behave that way,
and we create fake .DLL files in system32.
They are real PE files from their file header, but they do not contain the
implementation. When an app tries to LoadLibrary this DLL we load the builtin
one instead
So we
