ID Number: Q80402
1.00
WINDOWS
buglist1.00
Summary:
When compiling a Visual Basic application, if another project has
previously been loaded into the Visual Basic environment, the
resulting compiled application may contain information from the
previously loaded project. This can result in an overly large .EXE
file.
Microsoft has confirmed this to be a problem in Microsoft Visual Basic
programming system version 1.0 for Windows. We are researching this
problem and will post new information here as it becomes available.
More Information:
Workaround
----------
To prevent the inclusion of code from a previously loaded project,
exit Visual Basic, restart Visual Basic, load your project, then
compile it. This method will guarantee a minimally sized .EXE file.
Steps to Reproduce Problem
--------------------------
1. Start Visual Basic.
2. From the File Menu, choose Open Project (ALT, F, O) and enter
SAMPLES\ICONWRKS\ICONWRKS.MAK (or equivalent path) to load the
IconWorks example application.
3. From the File Menu, choose New Project (ALT, F, N) to create a new
project.
4. From the File Menu, choose Make EXE File (ALT, F, K) enter
PROJECT1.EXE as the .EXE file name and choose the OK button.
5. From the File Menu, choose Exit (ALT, F, X) to exit Visual Basic.
6. Start Visual Basic again.
7. From the File Menu, choose Make EXE File (ALT, F, K), enter
PROJECT2.EXE as the .EXE file name, and choose the OK button.
8. Compare the sizes of PROJECT1.EXE and PROJECT2.EXE.
PROJECT1.EXE will be significantly larger than PROJECT2.EXE.
For more information on minimizing the size of a Visual Basic .EXE
file, query on the following words:
Visual Basic Optimize Size Speed
Additional reference words: 1.00