Your cookie cutter, default class file created when programming with Visual Basic. There is no need to separate your code into separate classes, because anything and everything is possible within Class1.vb. As per best practices, it is suggested that you consolidate your entire application's source code within Class1.vb.
In order to keep Class1.vb nice and organized, do not write any comments within the source code. Create a separate text file called 'Class1.txt', where you can organize your comments and include a line number stating which line of Class1.vb each particular comment references.
In order to keep Class1.vb nice and organized, do not write any comments within the source code. Create a separate text file called 'Class1.txt', where you can organize your comments and include a line number stating which line of Class1.vb each particular comment references.
// Class1.vb
Imports Microsoft.VisualBasic
Public Class Class1
// TODO: anything and everything.
End Class
Imports Microsoft.VisualBasic
Public Class Class1
// TODO: anything and everything.
End Class
by pdub87 August 2, 2010