|
|
 |
 v2.0
|
|
| vbExport
v2.0 is a revolutionary breaktrough in Visual
basic exporting technology. Using Native
Export Technology, Visual Basic is the
only product which can export your Visual Basic
functions and routines in DLL's, EXE's and OCX's
with real Native compilation.
To better understand the present concepts of exporting
technologies, we have provided graphical representations
of different exporting methods. Although these
are only conceptual, they may be more or less
what other products do in order to export your
functions. |
| Figure-1
shows how Aliasing works. This dynamic
method of exporting is not very reliable
for a few reasons. (1) It may consume
more global overhead than necessary to
export a function, (2) degredation in
performance/speed may occur and (3) your
function truly is not exported. Only a
referenced table is available through
which, the embedded object in your project
provides the availability to your function. |
Figure-1
 |
|
Figure-2
demonstrates the idea of post-compile
time patching. In this example, we can
see how the patching application calls
Visual Basic to compile the DLL, then
open the DLL and write code into it. This
causes major concerns with regards to
(1) Cyclic Redundancy, (2) system integrity
and (3) system usage and overhead.
There are certainly other concerns but
none as great as those mentioned. Post-compile
time patching is a nice concept, but hacking
is not an effective method in the development
process. |
Figure-2
 |
|
Figure-3
clearly shows that vbExport is integrated
in the Visual Basic IDE. As part of the
IDE, vbExport can understand your code,
parse, correct and properly compile your
entire project, whether DLL, EXE or OCX
and exprt all Public Functions.
Remember, only public functions which
are in a .BAS module can be exported within
your DLL, EXE or OCX project. |
Figure-3
 |
|
| <-
Back to previous page
|
|
