Before you distribute a finished part for reuse, you must export its interface to a part interface (.vbe) information file. If you are distributing an unfinished part for further development, use its part implementation (.vbf) information file. Package the part information file with dependent files used by the part. The following factors determine what file types you need to package:
The following table summarizes the code file types you need. You should also provide documentation, including installation or build instructions and any information about how to add the part to the parts palette.
| File type | Package for reuse | Package for further development | |
|---|---|---|---|
| Nonvisual | Visual | ||
| Part interface (.vbe) or implementation (.vbf) file | Yes (.vbe) | Yes (.vbe) | Yes (.vbf) |
| C++ header (.hpp, .hpv) files | Yes | Yes | Yes (.hpv) |
| C++ user source (.cpv) files | No | No | Yes |
| Resource header (.h, .hv) and source (.rc, .rcv) files | No | Yes, for text that the part consumer can translate | Yes (.hv, .rcv) |
| Resource DLLs | Yes, for part palette and composition surface icons | Yes, for icons, bitmaps, and text (including any translated text that you provide) | No |
| Interface DLL | No | Yes | No |
| Runtime DLL | Yes | Yes | No |
| Import library (.lib) file | Yes, for dynamic linking on OS/2 and Windows | Yes, for dynamic linking on OS/2 and Windows | No |
Exporting a Part Interface for
Reuse
Adding Part Information for
Visual Composition
Sharing Parts with Other
Programmers
