http://bugs.winehq.org/show_bug.cgi?id=9422
--- Comment #29 from Anastasius Focht focht@gmx.net 2008-11-13 17:56:25 --- Hello,
--- quote --- We have a test that shows that gdiplus on windows behaves the same way we do when given a version of 2. It fails. --- quote ---
--- quote --- I suspect a similar situation to bug 14980 (Visio including a newer version of gdiplus that it installs for office only and expects to use). --- quote ---
Sure, it's a similar situation as in bug 14980 (OS vs. Office RichEdit). Office 2003 distributes it's own -private- GDI+ 1.1 which is loaded with full path. That's why I told to modify the load order setting in earlier comments so the correct (private) native gets picked up.
There are gazillion of GDI+ versions distributed with apps and Windows versions - either in private paths or in side-by-side GAC. The only thing that matters is major file version.
GDI+ 1.0 -> 5.x file version GDI+ 1.1 -> 6.x file version (only shipped with Vista and some Office products)
--- quote --- That's correct, asking for gdiplus version 2 fails under Vista as well. --- quote ---
Because you loaded GDI+ 1.0 and not 1.1. Search your casual Windows partition - you might end up finding several gdiplus.dll scattered everywhere.
Apart from "private" versions, Gdiplus is a side-by-side assembly, deployed in SxS GAC. You either load GDI+ 1.1 using full path at run time or explicitly add an 1.1.xxx.xxx gdiplus.dll manifest dependency in application manifest so loader will pick up the right one.
Regards