there's a lot ov VB6 functionality that is present in .NET, but in a different way. To assist with this and give developers an easy way to migrate code form VB6 to VBN, they created the Microsoft.VisualBasic namespace
as a simple example that we just finished discussing in another thread:
In vb6 we wrote MsgBox("Hello"). Now we write MessageBox.Show("hello")
F2 still gets you the object browser, so you can search for MessageBox and MsgBox and see the differences..
When you feel ready to take the plunge to pure .net code without the Microsoft.VisualBasic assistances (and understand there is no set rule saying you must do so) you can remove the reference to Microsoft.VisualBasic in the project's properties and all the bits of code you wrote that rely on the legacy compatibility provided by this suite, will become compiler errors.. at that time Im sure you can visit here and ask .e.g what the equivalent of CDate or CStr are..
-
In a more general sense, oyu need to be aware that VBN is a fully developed, well engineered language of its own that shares a bit of vb6 syntax and some familair words like Form, Control. As such you might do well to get a good book on it, as youre suddenly dealing with a proper Object Oriented, multithreaded language - there's a few paradigms that are very different to VB6 (like if you wanted to make all the forms in your program have a fade effect when closed, you might use inheritance to do this- VB6 has no scope for this) and its really a modification to the way you think about programming, and its rather hard to explain!