PRB: VB 4.0 EXEs Are Different When Compared Byte-by-Byte (129288)
The information in this article applies to:
- Microsoft Visual Basic Control Creation Edition for Windows 5.0
- Microsoft Visual Basic Professional Edition for Windows 5.0
- Microsoft Visual Basic Enterprise Edition for Windows 5.0
- Microsoft Visual Basic Standard Edition, 32-bit, for Windows 4.0
- Microsoft Visual Basic Professional Edition, 16-bit, for Windows 4.0
- Microsoft Visual Basic Professional Edition, 32-bit, for Windows 4.0
- Microsoft Visual Basic Enterprise Edition, 16-bit, for Windows 4.0
- Microsoft Visual Basic Enterprise Edition, 32-bit, for Windows 4.0
This article was previously published under Q129288 SYMPTOMS
When making two executables in a row from the same project no matter how
small, the .EXE files will come out with a difference in bytes when using
the FC (File Compare) utility. No two executable files created from the
same Visual Basic source code are identical. While the file sizes may
be the same between two .EXE files, a byte-by-byte comparision reveals that
the actual .EXE files are different.
CAUSE
Many internal identifiers and GUIDs that may be used in the application are
reassigned on every compile. A few of these are written out into the .EXE
file in internal tables. Also, the Win32 file format has an entry in it for
the time stamp of the executable. This will be set to a different value
each time you make a new .EXE file.
STATUS
This behavior is by design.
Modification Type: | Major | Last Reviewed: | 12/9/2003 |
---|
Keywords: | kbprb KB129288 |
---|
|