How to do development and build visual basic 6.0

Question

I am looking for best practice in creating several visual base projects (all dlls). We have several projects, and our final version will be dll. Now one project uses 2 other projects, and the other belongs to another project. Should projects link to vbp or dll files? If they reference vbp files, how to build all projects?

Answer 1

After a few years with VB6, our projects, as a rule, were structured as follows:
All project sources (project and source) are organized in the source folder.
\ Project \ source
\ Project \ source \ project1 \
\ Project \ source \ project2 \
...
All binary files (.dll and .exe) in one bin folder.
\ Project \ Bin \

All .dlls are installed as binary files that are compatible with the resulting file in a single bin directory.

, , build.cmd, , , :
" c:\Program Files\Microsoft Visual Studio\VB98\VB6.EXE"/M.\source\project1\proj1.vbp
" c:\Program Files\Microsoft Visual Studio\VB98\VB6.EXE"/M.\source\project2\proj2.vbp
" c:\Program Files\Microsoft Visual Studio\VB98\VB6.EXE "/M.\source\project3\proj3.vbp
del.\bin\*. exp
del.\bin\*. lib

.
, , VB .
, build.cmd .

Answer 2

VB, . , VB , .

Preserve, . , , , ( COM +, dll)

, ( , Vb6, , .vbg ).

Visual Build, Visual Make, .

Answer 3

, .

VB6 . -

A ( A, )

A

B, A

B

C, B A

C .

..

, typelibs COM DLL INCLUDE typelibs , . Libs VB6 COM DLL OLE View, Visual Studio 6.0.

DLL, MS- Typelibs . , .

, 90% , DLL- .

, , .

Note that these problems only occur when you add what other DLLs refer to and they need to maintain binary compatibility.

You need a system to ensure that everyone has the right set of compatibility dlls to create against.