GDI plus in .net 2.0 advantages
I have a winforms app in .net 1.1 that extensively uses GDI instead
of controls on forms, as there is lot of content.
Now, we are migrating to VS 2005 on .net 2.0.
What are the features of the GDI+ in .net 2.0 that I should look
at leveraging How different is it from the GDI of 1.1

GDI plus in .net 2.0 advantages
Abhi Win
Sree2000
I don't know if there have been any significand changes to GDI+ in 2.0, but I know that there's now in fact better support for GDI (with the TextRenderer class for example) since some people had problems using GDI+.
CharlesJ
See also this post for a comparo of ControlStyle flags and the property. http://forums.microsoft.com/MSDN/ShowPost.aspx PostID=14701&SiteID=1
Philip Jaques
DGV isn't an area of deep expertise for me, but it's highly doubtful you could craft a rendering algorithm significantly more efficient than what is there. Are you using all the right modes for the DGV (virtual) to get the best perf
St3veM
Bissy
http://www.msdn.microsoft.com/netframework/programming/classlibraries/apiusability/
Waseem Aslam
In another instance, I found gdi painting to be lot less memory intensive than user controls. That is why I would like to profile both approaches and compare.
Marcel Meijer
Another related question.
I have a datagrid view on in my smart client app that is expected to display
a large number of records.
Client memory is at a premium in my setup, and I would like to optimize that.
In this scenario, would it make sense to use GDI rendering to replace
datagrid view control
fly_eye
Mind though, that the BufferedGraphics.Render method does not clip against GDI+ regions:
http://lab.msdn.microsoft.com/ProductFeedback/viewfeedback.aspx feedbackid=9dd77247-66db-4fff-b30e-2a97ba72a89e
I do have the feeling that GDI+ isn't really a focus for Microsoft anymore, with the arrival of WPF/Avalon. Correct me if I'm wrong, but I believe there are still some outstanding bugs from .NET 1.1 that weren't fixed.