Hi Sameer,
for every class ( a form isn`t anything else ) the first thing which is be called is the Sub New() method, but before the code in this New() method is executed the variables which are declared in the declaration part of the class and which are actually createing an
new instance of some class are initialised first.
As an example:
The order of execution/initialisation will be:
'Visual Basic 2008 - .net 3.5 - Any CPU
Public Class Form1
Private var1 As New String("1"c, 1)
Private var2 As Point = New Point(1, 1)
Private var3 As testclass
Private var4 As New testclass
Public Sub New()
InitializeComponent()
var3 = New testclass
End Sub
End Class
Public Class testclass
Private var1 As Point
Private var2 As Point = New Point(1, 1)
Public Sub New()
var1 = New Point(1, 1)
End Sub
End Class
- Form1.New() will be called
- Form1.var1 will be created as a new instance of the String class
- Form1.var2 will be created as a new instance of the Point class
- Form1.var4 will be created as a new instance of the testclass class
-> the New() method of the testclass will be called
- testclass.var2 will be created as a new instance of the Point class
-> the code inside the New() method will be executed
- testclass.var1 will be created as a new instance of the Point class
- the code inside the Form1.New() method will be executed
->
- Form1.var3 will be created as a new instance of the testclass class
-> the New() method of the testclass will be called
- testclass.var2 will be created as a new instance of the Point class
-> the code inside the New() method will be executed
- testclass.var1 will be created as a new instance of the Point class
Hannes
If you have got questions about this, just ask.
In a perfect world,
users would never enter data in the wrong form,
files they choose to open would always exist
and code would never have bugs.
C# to VB.NET:
http://www.developerfusion.com/tools/convert/csharp-to-vb/
