Home > SOA Tips > .NET Developer > Working with graphics
SOA Tips:
EMAIL THIS
 TIPS & NEWSLETTERS TOPICS 

.NET DEVELOPER

Working with graphics


Jim Mischel
04.20.2004
Rating: -4.00- (out of 5)


Digg This!    StumbleUpon Toolbar StumbleUpon    Bookmark with Delicious Del.icio.us   


The first step in working with graphics in .NET is understanding the contents of each graphics related namespace. In this tip from Jim Mischel's .NET Resource Center from InformIT, he takes a look at the contents of the graphics namespaces.


The .NET Framework includes a rich set of managed classes that serve as wrappers around GDI+, the Windows XP graphics API. GDI+ improves on the original Windows Graphics Device Interface by providing new features and optimizations. The .NET Framework managed classes create an object-oriented and easy to use interface to the GDI+ graphics facilities, and completely insulate the programmer from the need to manage display contexts, handles, and other Windows graphics arcana. The programming model isn't completely different from GDI, though. If you've done Windows GDI programming you'll be right at home with the managed classes, and happy to be freed from worrying about the more mundane aspects of managing device contexts, handles, and graphics objects.

The .NET graphics API is fully contained in the System.Graphics namespace. System.Graphics contains classes that perform basic drawing functions, and namespaces that provide more specialized functionality. The table below briefly describes the contents of each of the namespaces.

Contents of System.Drawing namespaces
NamespaceContents
System.DrawingContains classes that encapsulate basic
graphics objects including pens, brushes,
images, points, rectangles, colors, and fonts.
System.Drawing.DesignProvides user interfaces for selecting or
defining bitmaps, fonts, images, and other
graphics objects.
System.Drawing.Drawing2DIncludes classes that provide advanced
two-dimensional and vector graphics
functionality, including gradient brushes,
geometric transformations, and graphics paths.
System.Drawing.ImagingClasses in this namespace provide
advanced imaging functionality, including
metafiles and classes that allow the GDI to
be extended to work with any image file format.
System.Drawing.PrintingProvides print-related services,
including print preview.
System.Drawing.TextProvides enhanced text-handling capabilities,
specifically in the area of fonts.

You'll find that most of your graphics work will be with classes defined in the System.Drawing and System.Drawing.Drawing2D namespaces.


Learn how to draw lines and curves in .NET at InformIT.


Rate this Tip
To rate tips, you must be a member of SearchSOA.com.
Register now to start rating these tips. Log in if you are already a member.




Digg This!    StumbleUpon Toolbar StumbleUpon    Bookmark with Delicious Del.icio.us   



RELATED CONTENT
Microsoft .NET Web services
Microsoft preps .NET 4.0 - framework improves on REST, MVC, JQuery support
How do I balance throughput requirements and interoperability?
APM software traces transactions across tiers, technologies
How you can learn M Grammar for Oslo modeling
Legacy modernization opens Windows for publisher
Former .NET Web developers ride Ruby and Rails application framework
Microsoft Oslo at PDC: Dial 'M' for modeling language
Yahoo proxy fight looms
New Microsoft site for architects
LAMP coders go hybrid route
Microsoft .NET Web services Research

Platforms and Servers
Tracking down managed memory leaks
Handling exceptions in .NET
.NET Compact Framework graphics
The Data Access Application Block
Decision time: .NET or J2EE?
A great .NET resource: .Net2TheMax
Delegates vs. interfaces in .NET
Project structure best practices
Working with PDFs in a .NET environment
Displaying errors with the error provider

.NET Developer
Programming Indigo
DataSets and Web services don't mix
Security in .NET 2.0
Tracking down managed memory leaks
Handling exceptions in .NET
.NET Compact Framework graphics
The Data Access Application Block
A great .NET resource: .Net2TheMax
Delegates vs. interfaces in .NET
Project structure best practices

RELATED GLOSSARY TERMS
Terms from Whatis.com − the technology online dictionary
Common Language Infrastructure  (SearchSOA.com)
Visual J#  (SearchSOA.com)

RELATED RESOURCES
2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems
Search Bitpipe.com for the latest white papers and business webcasts
Whatis.com, the online computer dictionary

DISCLAIMER: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.



SOA Trends and Strategy - SOA Education, SOA Development, SOA Implementations
About Us  |  Contact Us  |  For Advertisers  |  For Business Partners  |  Site Index  |  RSS
SEARCH 
TechTarget provides technology professionals with the information they need to perform their jobs - from developing strategy, to making cost-effective purchase decisions and managing their organizations' technology projects - with its network of technology-specific websites, events and online magazines.

TechTarget Corporate Web Site  |  Media Kits  |  Site Map




All Rights Reserved, Copyright 2001 - 2009, TechTarget | Read our Privacy Policy
  TechTarget - The IT Media ROI Experts