Open GoogleCodeExporter opened 9 years ago
I am betting you are on Windows XP.
I am having the same problem with Windows XP, while on Windows 7 everything
works out of box.
I've tried setting up dependantAssembly as following:
<dependentAssembly>
<assemblyIdentity name="WebKit.Interop" publicKeyToken="b967213f6d29a3be" />
<publisherPolicy apply="yes" />
<bindingRedirect oldVersion="0.0.0.0-65535.65535.65535.65535" newVersion="533.0.0.0" />
<codeBase version="533.0.0.0" href="WebKit\WebKit.Interop.dll" />
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="WebKitBrowser" publicKeyToken="b967213f6d29a3be" />
<publisherPolicy apply="yes" />
<bindingRedirect oldVersion="0.0.0.0-65535.65535.65535.65535" newVersion="0.5.0.0" />
<codeBase version="0.5.0.0" href="WebKit\WebKitBrowser.dll" />
</dependentAssembly>
this doesn't work, as on Windows XP App looks for webkit.dll in App Folder,
even if all assemblies are loaded from WebKit subfolder.
Also tried:
- forced loading of assemblies (preloading with Assembly.LoadFrom(...)):
(XP) doesn't work, assembly is loaded again after with incorrect paths
(W7) not tested, but I guess it doesn't work.
- forced loading of webkit.dll (calling function in webkit.dll forces loading
of dll):
(XP) webkit.dll and its dependecies are loaded properly, but again when referencing assembly is loaded webkit.dll is loaded from incorrect location
(W7) not tested.
- SetDllDirectory() force location for webkit.dll and its files:
(XP) can force loading of assembly but webkit.dll loading fails.
(W7) not tested
- Setting in Environment Path WebKit as member of path variable:
(XP) can force loading of assembly but webkit.dll loading fails.
(W7) not tested
NOTE @MS: I thought DLL's are kept in memory, and not reloaded over and over
again?
Original comment by niger...@gmail.com
on 15 Oct 2013 at 12:15
Original issue reported on code.google.com by
wuhika...@gmail.com
on 8 Oct 2012 at 8:00