I agree that most of the code containing these methods will have to be massively rewritten.
However, I had a problem in that the sheer number of occurrences of these went over a thousand and made it difficult for me to work on the code. I therefore wrote a class that had methods with the same name and then did a quick replace of VB6 with
the name of my class containing the stubs. I was able to go through pretty quickly with the Next button on Quick Replace. I wanted to quickly check each occurrence to make sure that I wasn't changing things that I shouldn't.
PrintForm1 is not a member of System.Windows.Forms.Form
The variable from which you are apparently referencing the property PrintForm1 (e.g. MyForm.PrintForm1) is probably defined as System.Windows.Forms.Form and you are setting the value of MyForm to the form that you are processing. (Dim MyForm As System.Windows.Forms.Form)
You have to use the actual class of the form in the Dim statement to make the properties of the form visible or else cast it to the same class as the actual form using the CType statement. I assume that PrintForm1 is some element of the form.
Dim g As Graphics = Me.CreateGraphics()
In the code setting up a form the variable Me is set to the id for the form itself. If you are calling this from a module (code that is not part of a form), you have to replace Me with the id of the form. One trick is to put the following line
in the code for the form
Public Shared RemoteCall As System.Windows.Forms.Form
and then place a line in the handler for the load event that reads
RemoteCall = Me
You can then get the id of the form by knowing the class name of the form.