When the Log Build option is checked on the logging tab of the general options window, VBLM logs the modifications that it makes to the copies of your source code when you command VBLM to build a localized version of your project(s). The disk file (VBLM Build Log.txt by default, but you can change this) is written to the same directory as the parent VB project.
The changes logged include line-by-line changes:
============================================================
VBLM Build Log: 20-Mar-02 11:11 AM
VB Project = C:\Program Files\DevStudio\VB\samples\PGuide\Optimize\Optimize.vbp
Action = Building Pig Latin version in C:\Program Files\DevStudio\VB\samples\PGuide\Optimize\Pig Latin
C:\Program Files\DevStudio\VB\samples\PGuide\Optimize\Collectn.frm
Line 4
Orig: Caption = "Collections"
VBLM: Caption = "ollectionsCay" 'VBLM replaced "Collections"
Line 15
Orig: Caption = "For Next"
VBLM: Caption = "orFay extNay" 'VBLM replaced "For Next"
When VBLM builds a runtime switched version, the build log documents the line-by-line replacement of strings with function calls as well as the more extensive code modifications needed to support runtime switching
Line 63
Orig: Debug.Print "bState Unknown."
VBLM: Debug.Print VBLM_RTString(SC0372) 'VBLM replaced "bState Unknown."
C:\Program Files\DevStudio\VB\samples\PGuide\Optimize\Multilingual\x\Numbers.frm, Constant Revisions
Line 449
Orig: Debug.Print WW2
VBLM: Debug.Print VBLM_RTString(SC0122) 'vblm modification: replaced reference(s) to "WW2"
Trigger control for on-the-fly runtime switching added to Numbers.frm
Call to VBLM_Setproperties added to existing initialization event in Numbers.frm
VBLM_Setproperties subprocedure added to Numbers.frm
Trigger control change event for on-the-fly runtime switching added to Numbers.frm
As with all logs, whether or not VBLM overwrites or appends to a pre-existing log depends on your setting on the logging tab. The build log is set by detault to overwrite.
See Also