[Bug 33384] Basic WPF applications using .NET 3.5 WPF fails to handle images (windowscodecs {7543696a-bc8d-46b0-5f81-8d95728972be} = IMILBitmapSource unsupported)

wine-bugs at winehq.org wine-bugs at winehq.org
Tue Apr 23 15:51:33 CDT 2013


http://bugs.winehq.org/show_bug.cgi?id=33384

Anastasius Focht <focht at gmx.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #44216|0                           |1
        is obsolete|                            |

--- Comment #21 from Anastasius Focht <focht at gmx.net> 2013-04-23 15:51:33 CDT ---
Created attachment 44273
  --> http://bugs.winehq.org/attachment.cgi?id=44273
Patch "v4" based on Dmitry's "try3" with additional unknown interface/method
stub added and BitmapImpl layout tweak

Hello Dmitry,

--- quote ---
Looks like the differences observed are caused by the fact that we use
different versions of .NET. I used 'winetricks dotnet35', while it seems that
your version
is 3.0. Also your backtraces indicate a crash in wpfgfx_v0300, while I have
crashes in milcore.dll.
--- quote ---

Actually I was working with a .NET Framework 3.5 SP1 WINEPREFIX (even if the
crash backtraces suggest something with "3.0").

I created more prefixes for testing:

.NET 3.0
.NET 3.0 SP1
.NET 3.5 (winetricks install currently broken, recent msxml3 regression/new
bug? Needs native msmlx3 now)
.NET 3.5 SP1 (same as .NET 3.5, recreating didn't work anymore with plain
winetricks recipe)

To my surprise your patch combined with my findings _already_ worked in a .NET
3.0 prefix.
The WPF test application shows the "beta" picture. Yay!

It's .NET 3.5 SP1 MIL that seems to behave differently and needs further
investigation (different engine/usage?).

I attached a new version "v4" patch based on your "try3" with my findings.
The method stub "IMILUnknown2Impl_UnknownMethod1" has to return something
different than S_OK, otherwise it crashes in all 3.x prefixes.

Can you test it with your installation?
At least we've got something with surprisingly little implementation effort.

Regards

-- 
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.



More information about the wine-bugs mailing list