GDIPlus.TLB  includes all the Constants, Declares, Enumerations and Structures(UDT) from the Platform SDK as well as some general Win API support:

To see the library in use, check out:

• GDI+ Unicode Logo project at http://www.Planet-Source-Code.com/vb/scripts/ShowCode.asp?txtCodeId=42861&lngWId=1
• Demos using the TLB at http://www.Planet-Source-Code.com/vb/scripts/ShowCode.asp?txtCodeId=43004&lngWId=1
• The GDI+ COM Wrapper and associated samples  in the VB Media Code section at http://www.vbAccelerator.com.

More related postings although not using this TLB can be found by searching 'GDI+' at http://www.Planet-Source-Code.com/vb
 

Code that works with internal declares may behave differently(even crash) using the Tlb. Most if not all of these problems can be traced to one or more of the following:

• Incorrect parameter type in the TLB declare. Try a local declare to override the TLB to see if this is true. Please report any problems so we can fix it.
• Passing illegal parameters.
• Passing paramaters using the wrong format.
  For example encoderParams needs to be a structure in memory containing first a long variable containing count, followed by an array of arbitrary EncoderParameter structures. This must be laid out as a memory pointer and leads to a thorny coding problem in VB and in the Type Library: How do you declare the parameters you're going to pass if you don't know how many of them there are or anything about how their data is laid out in memory?
  There are no standard answers to these kinds of questions. The only real way around them is to work out what would be expected in memory and build it up as best you can, using a combination of structures, byte arrays, and memory allocations as required.
• Not deleting objects that you create or trying to create a new object without first releasing the old one. At minimum this will cause a memory leak and quite often a GPF.
   

By using a TLB in lieu of Declares you not only eliminate cut and paste but more important is that your compiled Exe only includes the TLB items that are used.
Type Libraries are usually required only at design and compile time. Once the project that uses it is compiled the type library is not required anymore. So the library size does not matter because you do not have to include it in the installation package.

Another major advantage is that you can pass a Unicode string directly without having to use a Byte Array or StrPtr.

IStream, IPersistStream are not included. TLBs that support these interfaces can be found at:
 

Name	URL	Comments
OLELIB.TLB	www.domaindlx.com/e_morcillo/	Supersedes Strm.Tlb
ISTORAGE.TLB	www.vbbyjc.com/
STRM.TLB	www.vbaccelerator.com	Now included in OleLib.Tlb
VBACOM.TLB	www.vbaccelerator.com

Other Gdiplus TLBs available for Vb

Gdiplus Classes available for Vb