I have been away from work a bit for this week and the last due to presenting some plans and also this week was my birthday (well, yesterday was my birthday). Without furthyer adieu, a few updates for the centers:
Use this not thatWhen targetting Windows Vista and later, use Direct2D instead of GDI. This is a tough one because GDI has been around and has been supported for a long time and is unsupported in older Windows versions such as Windows XP (don't quote me on that ^_^). Many developers have GDI in the core of their applications and have opted to use it over newer technology such as GDI+ due to complexities with more modern APIs. GDI also has great interoperability across Windows versions and SKUs. That said, we have made a significant investment in making Direct 2D easy to integrate into applications and it has significant advantages over GDI. For example, Direct 2D enables you to take advantage of hardware accelleration and other compositing features that will make your app shine. Also, Direct 2D is a great migration path from GDI because of its great interoperability features. From MSDN: Integrating Direct2D-based rendering is made easier for developers through surface-level interoperability with GDI and Direct3D. Applications that render content primarily with GDI, GDI+, or Direct3D, can begin by using Direct2D to render specific areas of their application, and over time move to a model where rendering is performed primarily via Direct2D, using GDI primarily for plug-ins or legacy extensibility. You can use D2D in a portion of your app and slowly migrate more of your app into it as you have resources to do it.
In short, going with Direct2D instead of GDI will make your app look better and perform better. If you are looking to just target Windows Vista and later, D2D will really make your app stand out. If I've convinced you, you're probably wondering where to get started with D2D. I like to start with samples, so I'll recommend the Direct 2D samples. There are a number of excellent samples there like Multi-Sample Anti-Aliasing in Direct2D:
Multi-Sample Anti-Aliasing in Direct 2D
Compares Multi-Sample Anti-Aliasing (MSAA) and Per-Primitive Anti-Aliasing (PPAA) techniques in different scenarios and demonstrates which technique is suited for which scenario.
Download Multi-Sample Anti-Aliasing in Direct 2D
Also, there are some great articles on getting started with Direct2D but the Direct2D developer quickstart is the most concise documentation that I have seen for getting you going.
So, for ASP.NET server-side image composition and rendering (in C#), what should we use?
Ok a suggestion, I have been trying to manipulate the binaray codes combined with artifical intelligence writting so that people cannot write can tape their lecture and connect it to thier pc and have it translate voice into binary codes to give them a set of printed actual said notes taken straight from the proffersor on micro digital tape less voice recorder, because all people do not learn in the same format . just an idea !!!!
@Nathanael: It depends on what you're doing but if you're doing everything server-side and are interested in image composition, you should be able to use WIC - msdn.microsoft.com/.../ee719902(VS.85).aspx which was released with Vista. You could also use D2D with a Bitmap render target.
That said, I'm not as informed in the C# arena and there may be a better solution, you might want to try asking on ScottGu's blog: http://weblogs.asp.net/scottgu - at a minimum it'd raise the scenario as important to customers.
@Jeffrey: Thanks for the suggestion! There are some great speech-to-text APIs coming with the Mango release of WP7, it might be a good starting point.