Overview of Visual Basic Application Creation

VB Modules

It is important to note that all VB projects are merely a collection of files of codes called "modules". There may be some confusion since modules ending in ".bas" are grouped as "modules" when actually all the others are actually modules as well.

.vbg
Visual Basic Group project file. A list which enable a developer to work with multiple projects at once.
.vbp
Visual Basic Project file. A list of all the modules associated with the project, including information about the environment options you set.
.frm
FoRM  modules. A form module is text file that describes the form and its controls, including property settings. A form is a visible user interface, usually a window and its various parts (controls). A form module can also contain form-level declarations of constants, variables, and external procedures, event procedures, and general procedures.
.frx
FoRm Data Files. A binary data file automatically generated by Visual Basic for each form in the project. This includes data for pictures and icons. (These won't show as part of a project in the IDE, but the files are there nonetheless.)
.cls
CLaSs modules. These are modules that, unlike form modules, have no visible interface. Classes are used to create objects. The class module has the code for its members, i.e. properties, methods, and event procedures. Class modules are good for storing code that can be shared with other applications.
.bas
Standard modules. (The extension is derived from "BASIC"). Standard modules contain items of global or local scope (unlike the items in form modules which are usually of local scope). These items include declarations of types, constants, variables, external procedures, and global procedures. Standard modules are good for storing code that can be shared with other applications.
.ctl and .pag
User ConTroL and property PAGe modules. The are similar to forms but are used to create ActiveX controls.
.ocx
ActiveX controls. Optional controls that can be used in forms. Visual Basic comes with some but you can make your own ActiveX controls or get others made by others.
.dob
ActiveX documents. Similar to forms but viewed by Internet browsers.
.dsr
Active DeSigneR files. A file automatically generated by Visual Basic that stores information about the designers involved in the project. This includes Data Environment Designers and Data Report Designers.
.res
RESource files. A file that contains data such as bitmaps and text strings. Only one resource file can accompany each project. The file can be changed without having to recompile.
misc
There can also be any number of other files which were created by other programs that can be accessed by a Visual Basic project.

Project Types

At the start of a project, a project template must be chosen. Each template  supports the development of different kinds of applications and components by providing the appropriate basic project objects and environment settings. The following are typical project templates:

Standard EXE
The choice for normal stand-alone application. By default this template starts with one form.
Data Project
The choice for applications that read or manipulate data from a data source. Note: a standard EXE project could be also deal with data but the you would have to manually set references to data-specific components such as the MS ActiveX Data Objects (ADO) library. By default this template starts with a DataEnvironment object and a DataReport object.
ActiveX DLL/ActiveX EXE
The choice for developing COM components that expose functionality to other applications. The DLL variation exposes functionality programmatically to another application whereas the EXE variation can also run as a stand-alone application. By default these templates start with a class module.
ActiveX Control
The choice to create a component to be used as a user interface element in a form. By default this template starts with a UserControl object.
ActiveX Document EXE/ActiveX Document DLL
The choice to create components designed for use in a document object container, eg a browser. This is a variation on OLE usage. By default these templates start with a UserDocument object.
DHTML Application
The choice to create components that can be used on the client side of Web applications. The client would probably use a DHTML compliant browser like MS IE 4. By default this template starts with a class module and a DHTMLPage object.
IIS Application
The choice to create components that can be used on the server side of Web applications. The server would probably be, MS IIS. By default this template starts with a WebClass object.

At the end of a project, it is easy to compile a Visual Basic project into an executable file. Go to File menu and click Make ProjectName.exe. The other option would be to compile it from MS-DOS. EG:

vb6 /make projectName

Page Modified: (Hand noted: ) (Auto noted: )