> Icon.ExtractAssociatedIcon() has no parameters. Surely we need all the
> sizes of icons when we actually writing applications, but it seems
[quoted text clipped - 3 lines]
> isn't, what the heck is the rationale for providing only 32*32?) Thank
> you.
On Apr 1, 12:26 am, "Willy Denoyette [MVP]"
<willy.denoye...@telenet.be> wrote:
> > Icon.ExtractAssociatedIcon() has no parameters. Surely we need all the
> > sizes of icons when we actually writing applications, but it seems
[quoted text clipped - 10 lines]
>
> Willy.
Ah... I hope Microsoft would provide more options for
ExtractAssicicatedIcon, when they make the next version of the .NET
Framework.
Thank you, Willy.
Willy Denoyette [MVP] - 31 Mar 2008 23:00 GMT
On Apr 1, 12:26 am, "Willy Denoyette [MVP]"
<willy.denoye...@telenet.be> wrote:
> "Sin Jeong-hun" <typing...@gmail.com> wrote in message
>
[quoted text clipped - 15 lines]
>
> Willy.
Ah... I hope Microsoft would provide more options for
ExtractAssicicatedIcon, when they make the next version of the .NET
Framework.
Thank you, Willy.
This has nothing to do with the framework, it's the underlying API
(shell32.dll) which only supports 32X32 bit ICON's.
All they could do is wrap the SHGetFileInfo, but this ain't gonna happen
because Windows.Forms will not get enhanced.
Willy.