Project NameCheck configuration
There are three tabs of settings related to the data type of names: Types, Controls and Modules. The Types tab deals with the "As Type" part of variables and functions. The Controls tab deals with VB classic controls. The Modules tab deals with modules, forms, classes and so on. Constants and enums are not affected by the settings described on this page.
The Types tab deals with the "As Type" part of variables, parameters, functions and properties (but not constants or Enums). It includes built-in types such as "Integer" and object types such as "Table". You can also add your own user-defined types like "TPerson" or Enums like "EClassification".
There are some special settings on Types tab. Here are the descriptions of these type settings.
The Controls tab deals with control names. You can specify standards for TextBox names, CommandButton names etc. A list of common control types is included, but you can add types for 3rd-party controls you use. See the Special tab for an additional setting for variables containing a control. The Controls tab has no meaning in VB.NET projects. In VB.NET, controls are declared as normal class-level variables.
The Modules tab deals with module names. You can specify standards for the names of Forms, Modules, Classes, .NET Structures, Namespaces, Interfaces etc. These names are special in that there is no scope checking for them. Usually modules are either Friend or Public, although VB.NET allows all scopes for them.
In VB 3-6, you can declare a variable as Form or MDIForm, for example. The settings on this tab affect also the type prefix/suffix of those variables.
The physical file names are not checked by Project NameCheck.
In most cases you will probably set prefixes for the various types, like "int" for Integer, "txt" for TextBox and "frm" for Form. Suffixes are most likely to come handy if you decide to accept type characters for built-in types: "%" for Integer, "$" for String etc.
Constants and enums are exceptional. None of the data type settings have any effect on them. Constants have their own prefix/suffix setting on the Special tab and Enum members have a similar setting on the Scopes tab.