Transition from Visual Basic 6.0 to Visual Basic.NET
I just downloaded the 'Transition from Visual Basic 6.0 to Visual Basic.NET'
(transitiondoc.doc) from Microsoft's website and there are few typos and
editing mistakes. In the hopes that a Microsoft employee is reading this
post, here what I found:
1) The Upgrade Wizard cell for Empty only has a period. It should say, "Empty
is converted to Nothing"
2) The Upgrade Wizard cell for Arrays is empty. It should say, "During upgrade,
you have the option to treat your arrays as zero lower bound, or to change
them to an array compatibility class, as in the following example:
Dim a(1 To 10) As String
is upgraded to:
Dim a As System.Array = VB6.NewArray(GetType(String), 1, 10)"
3) The Visual Basic 6.0 cell for Assignment says, "There are two forms of
assignment: Let assignment (the default) and Set assignment. Set assignment
cn.". It should say, "There are two forms of assignment: Let assignment (the
default) and Set assignment. Set assignment can be used only to assign object
references. The semantics of Let assignment are complex but can be summarized
If the expression on the right-hand side of the Let statement evaluates to
an object, the default property of the instance is automatically retrieved
and the result of that call is the value that was assigned.
If the expression on the left-hand side of the Let statement evaluates to
an object, the default Let property of that object is called with the result
of evaluating the right-hand side. An exception to this rule applies if the
left-hand side is a variant containing an object, in which case the contents
of the variant are overwritten."
4) The Upgrade Wizard cell for File I/O says, "The file I/O statements are
upgraded to the corresponding functions. For example, the following code:
Open nput )". It should say, "The file I/O statements are upgraded to the
corresponding functions. For example, the following code:
Open "MyFile.txt" For Input As #1
is upgraded to:
FileOpen( 1, "MyFile.txt", _
There are also a few other miscellaneous mistakes, such as extra blank spaces
and blank lines inserted at various places in the document.
BTW, this sucks:
> From the Command window in Design mode, you can execute IDE commands,
> but you cannot run individual parts of your application.
Being able to test a routine from the Immediate window without having to
create a test program is a *huge* time saver. Please add this back in.
-- Android Development Center
-- Cloud Development Project Center
-- HTML5 Development Center
-- Windows Mobile Development Center