Compiled Size of EXE Compared to WBT

Keywords:      compiled Winbatch Script Size

---

Question:

I'm wondering about compiled program size... Lets say compared to VB5. Does Winbatch compile smaller (including DLLs?

Answer:

You get more bytes for your money with WinBatch. Its cheaper on a per compiled byte basis. What a deal.

Anyway. The compiler has two options:

1. BIG EXE

   About the same size as WINBATCH.EXE+WBDxx34I.DLL+Your *.WBT source code minus a smidgen.

   Around 480K.

2. SMALL EXE

   About the same size as WINBATCH.EXE plus your *.WBT source code (minus a smidgen).

   About 90K.

   Requires presence of WBDxx34I.DLL.

   About 390K.

And if you have multiple modules calling each other, you have the choice of using multiple .EXEs (you only need one copy of the .DLL if the .EXEs are in the same directory and you choose Small EXE to compile with),

or you can call Encoded Callable Modules (.WBC files), which must be called from a compiled .EXE and can be thought of as a compiled .EXE but dependent on another compiled .EXE. The size of .WBC files is between 50 and 90% of the source code.

In my installation we have at the moment some 15 small .EXEs in 3 directories, plus about an equal number of callable .WBC files. The .EXEs range in size from 90-120 kb, and the .wbc's from 1-4k. The installation handles a fair chunk of network maintenance and user isntallations/upgrades for departmentally supported applications. The total system, including the above, 3 copies of the dll's, and auxiliary files is now bordering 4 megs in size (sheesh this is beginning to sound like an infomercial for WinBatch!)

In my opinion, a lot of bang for the size, once you get to multiple apps that can reuse the .DLLs and .WBCs.

---

Article ID:   W12773

Filename:   Compiled EXE Size Compared to WBT.txt