http://bugs.winehq.org/show_bug.cgi?id=10928
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |focht@gmx.net
--- Comment #14 from Anastasius Focht focht@gmx.net 2010-08-04 14:00:07 --- Hello,
--- quote --- Looking at the source code for actctx and judging from the size of the other activation context functions, I'm going to assume it should be a moderately easy fix? --- quote ---
I'd like to see a Wine implementation of FindActCtxSectionGuid() -> RtlFindActivationContextSectionGuid() too. I'm currently investigating/tracking some .NET bugs that can be partially made to work by resorting to native ole32, specifically COM context management (inter-thread marshalling of COM proxies, passing direct object references across apartments, context callbacks). Unfortunately a working implementation of FindActCtxSectionGuid() is needed as prerequisite or it will bail early. Mostly the app will yield some message like this before failure:
--- snip --- ... 0015:fixme:actctx:FindActCtxSectionGuid 00000001 (null) 4 {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx} 0x32e7b8 ... --- snip ---
If managed (.NET) mostly followed by following exception:
--- snip --- System.Runtime.InteropServices.COMException (0x80070078): Retrieving the COM class factory for component with CLSID {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx} failed due to the following error: 80070078. --- snip ---
There are other bugs that might benefit from it - though they all seem to indicate native ole32 override. I'm not aware of a sample app that makes direct use of FindActCtxSectionGuid().
Regards