Reverse Engineering Visual Basic 2005 Code

You can reverse engineer Visual Basic 2005 files into an OOM.

1. Select Language > Reverse Engineer Visual Basic to open the Reverse Engineer Visual Basic dialog box.
2. Select what form of code you want to reverse engineer. You can choose between:

   • Visual Basic files (.vb)

   • Visual Basic directories

   • Visual Basic projects (.vbproj)

3. Select files, directories, or projects to reverse engineer by clicking the Add button.
   Note:

   You can select multiple files simultaneously using the Ctrl or Shift keys. You cannot select multiple directories.

   The selected files or directories are displayed in the dialog box and the base directory is set to their parent directory. You can change the base directory using the buttons to the right of the field.

4. [optional] Click the Options tab and set any appropriate options. For more information, see Visual Basic Reverse Engineer dialog Options tab.
5. [optional] Click the Preprocessing tab and set any appropriate preprocessing symbols. For more information, see Visual Basic reverse engineering preprocessing directives.
6. Click OK to begin the reverse engineering.

   A progress box is displayed. If the model in which you are reverse engineering already contains data, the Merge Models dialog box is displayed.

   For more information on merging models, see the Comparing and Merging Models chapter in the Core Features Guide.

   The classes are added to your model. They are visible in the diagram and in the Browser, and are also listed in the Reverse tab of the Output window, located in the lower part of the main window.

• Visual Basic Reverse Engineer Dialog Options Tab
  The following options are available on this tab:
• Visual Basic Reverse Engineering Preprocessing Directives
  Visual Basic files may contain conditional code that needs to be handled by preprocessing directives during reverse engineering. A preprocessing directive is a command placed within the source code that directs the compiler to do a certain thing before the rest of the source code is parsed and compiled. The preprocessing directive has the following structure: