During string extraction, VBLM examines your VB project and extracts strings for translation. String extraction is both the first step in using VBLM to localize your project, and also a recurrent activity as your VB project changes, and as you tune the rules configuring VBLM to extract only strings that should be translated. To initiate string extraction:
a) if extracting for the first time, click New Project on the main file menu and select the VB project you wish to localize;
b) if re-extracting, select Extract Strings from the Actions menu, or click the Extract Now screen command;
c) adjust the string extraction options as desired;
d) click OK
VBLM reads the files, extracts the strings, and stores them, along with other project data, as a new in-memory VBLM project. When the main window fills with current project information, you're ready to translate.
Note 1: As discussed in Tips & Tricks and String Extraction Overview, there are many strings in your project that should not be translated, it is a good idea to extract as few of these as possible, and VBLM's extensive SX options help you do this. In the process, you'll iterate adjusting SX options, re-extracting strings, and examining the results.
Note 2: Every so often, I get an e-mail complaining that the SX options aren't working: "I put Foo on the function list, but nothing changed, the strings passed to Foo() are still there!" Keep in mind that changes made to SX options have no effect until VBLM uses them to re-extract the strings.