[quoted text, click to view] >Some clients get this error. Not reproduceable....i understand that it
>Windows runs out of resources...fine. All I want to know is where does
>Microsoft publish information about what will work with the framework and
>won't work? Example...how many controls can you have on a form/in your
>entire application/loaded at the same time. What type of video drivers are
>not supported by GDI? What known bugs are currently in the framework.
These are tough questions to give an accurate answer to - they are OS and
environment dependent but the following information should help (from a
developer on the Windows Forms team):
On Windows NT / XP platforms, there is a per-process 10,000 handle window
limit (handle usually equals control), but an application should really try
to use less than half that limit to maintain good performance (good rule of
thumb: 5000 window handles is a huge application. It’s bigger than Visual
Studio’s resource usage by a factor of ten).
On Win 9X the limits are much more severe. There is a single 64kb heap
allocated to user resources on Win9x - a reasonable limit on Win9x is
probably around 200 handles. Some types of controls on Win9x take far more
resources: Win9X may crash unexpectedly after creating around 250 combo
boxes (independent of the framework - this is a Win9x issue). If you are
targeting Win9x, you need to be very frugal.
If you are doing a lot of GDI+ drawing, note that GDI+ does not have the
same resource limits on Win9x that GDI does. It will use the entire
process heap, and is therefore limited by available memory. GDI on Win9x
is like USER it has a hard 64kb limit.
GDI+ uses DirectDraw for software emulation. As long as the video card
supports DirectDraw, GDI+ should work fine. Note that some features in
Windows Forms: namely alpha-blended (layered) windows and chroma
transparency are all hardware features and many drivers have trouble with
these features. ATI drivers are notoriously bad with layered windows.
--------------------
Joe Stegman
.NET Client Team
Microsoft Corp.
This posting is provided "AS IS" with no warranties, and confers no rights.
