DOCUMENT:Q161287  17-MAR-1997  [vbwin]
TITLE   :HOWTO: Register Add-ins for Visual Basic 5.0
PRODUCT :Microsoft Visual Basic for Windows
PROD/VER:5.00
OPER/SYS:WINDOWS
KEYWORDS:kbusage vb5all vb5howto VBKBAddIn VBKBRegistry kbhowto

======================================================================
---------------------------------------------------------------------
The information in this article applies to:

 - Microsoft Visual Basic Professional and Enterprise Editions,
   for Windows, version 5.0
---------------------------------------------------------------------

SUMMARY
=======

Add-ins created using Microsoft Visual Basic 4.0 will not appear in the
list of available add-ins when using Microsoft Visual Basic 5.0. This
behavior occurs when the add-in is installed after Microsoft Visual Basic
version 5.0 has been installed on the system.

NOTE: Microsoft Visual Basic version 5.0 only supports 32-bit add-ins.

MORE INFORMATION
================

Microsoft Visual Basic version 5.0 has moved the available add-in
registration from VB.INI to a new file, VBADDIN.INI. This new file is used
exclusively for Visual Basic add-ins.

However, add-ins written with Microsoft Visual Basic 4.0 are usually
written to register themselves automatically into the VB.INI file.
Therefore, Add-in Manager for Microsoft Visual Basic version 5.0 will be
unable to determine how to launch such an add-in.

NOTE: It is recommended that add-ins written for Microsoft Visual Basic
4.0 be updated to register automatically into the VBADDIN.INI file instead
of the VB.INI file.

Follow these steps to register add-ins written with Microsoft Visual Basic
4.0 for use with Microsoft Visual Basic version 5.0:

1. If Microsoft Visual Basic version 5.0 is currently running, click Exit
   from the File menu.

2. Properly install the add-in as per its installation instructions. If
   Microsoft Visual Basic version 5.0 is currently running, click Exit
   from the File menu.

3. From the Start menu, click Find.

4. Type "VB.INI" in the Named field. Click Find Now.

5. The VB.INI file will be found in the \Windows folder. Double-click
   VB.INI to edit it.

6. In the VB.INI file, find the section labeled [Add-Ins32]. Locate the
   entry for the installed Visual Basic 4.0 add-in. It should look like
   the following:

   [Add-Ins32]
   MyAddin.AddinClass=0

7. Copy the line "MyAddin.AddinClass=0" by selecting the entire line and
   then clicking Copy from the Edit menu.

8. From the File menu, click Exit. Click No when asked to save the VB.INI
   file.

9. In the Find window, type "VBADDIN.INI" and click Find Now.

10. The VBADDIN.INI file will be found in the \Windows folder.
   Double-click VBADDIN.INI to edit it.

11. Insert a new line at the bottom of the VBADDIN.INI file. Move the edit
   cursor to this new line.

12. From the Edit menu, click Paste. This will paste the line that you
   copied from the VB.INI into VBADDIN.INI.

13. From the File menu, click Save.

14. From the File menu, click Exit.

The next time Microsoft Visual Basic 5.0 is run, your add-in will be
available in Add-In Manager.

REFERENCES
==========

Microsoft Visual Basic 4.0 Programmer's Guide
"Installing Add-Ins", pages 105-106

Microsoft Visual Basic 5.0 online Help

Microsoft Visual Basic 5.0 Books Online

Additional query words: invisible
======================================================================
Keywords            : kbusage vb5all vb5howto VBKBAddIn VBKBRegistry kbhowto
Version             : 5.00
Platform            : WINDOWS
Issue type          : kbhowto

=============================================================================

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS
PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND.  MICROSOFT DISCLAIMS
ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES
OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  IN NO
EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR
ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL,
CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF
MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.  SOME STATES DO NOT ALLOW THE EXCLUSION
OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES
SO THE FOREGOING LIMITATION MAY NOT APPLY.

Copyright Microsoft Corporation 1997.