Microsoft recently started to distribute a new version of the Visual Basic 2005 Power Packs. 

Link to Download details: Microsoft Visual Basic 2005 Power Packs 2.0

Notably, the routines that are included help with the automatic Upgrade/Migration of VB6 to .NET.  From the MSDN web site:

" Overview

The new Line and Shape controls included in this version of the Visual Basic 2005 Power Packs are a set of three graphical controls that enable you to draw lines, ovals, and rectangles on forms and containers at design time making it much easier to enhance the look of your user interface. These new shape controls also provide events such as click and double-click allowing developers to respond and interact with end users.
The Printer Compatibility Library allows projects that used the Printer and Printers Collection in Visual Basic 6.0 to be upgraded without having to re-write your printing logic. By simply adding a reference to the library, declaring a Printer and making a few minor syntax changes, your project will be able to print using the Printers collection and Printer object as it did in Visual Basic 6.0. This version adds a new Write method to the Printer object which allows you to print text without a forced carriage return similar to the semicolon syntax used by Print method in Visual Basic 6.0.
The PrintForm component is designed to bring back the ability to easily print a Windows Form. With this the new PrintForm component you can once again layout the Windows Form exactly as you want it and allow your users to print the form as a quick report."

I'd like to relate this post with the one I did a few days ago related to performance (http://blogs.artinsoft.net/fzoufaly/archive/2007/0... ).  In the previous post I was arguing about the use of the VB6 Compat library from .NET applications.  Basically, I was arguing that the VB Compatibility library is written and distributed by Microsoft and therefore users should not be afraid to use it in their programs.  TThe same goes with the power pack Microsoft is now releasing.  The power pack contains a number of functions that are not directly addressed by the basic .NET framework but that are widely used and requested by VB programmers.  So what is the right solution?  Well, program them in .NET!!!  I mean, is there another way to provide functionality that is not by programming it?  Again, don't be afraid of using these routines more than you would be of any control you use in your app.  And also, do not worry about the performance hit!!