The information in this article applies to:
SUMMARY
The information below includes the documentation and workarounds for Visual
Basic 6.0. This information can also be found in the README.htm file that
ships with Visual Basic 6.0 on the Visual Basic 6.0 CD-ROM. Please see the
REFERENCES section of this article for a list of the Microsoft Knowledge
Base articles relating to the Visual Basic 6.0 readme.
MORE INFORMATION"Command-Line Safe" Add-In BehaviorYou can use the Load Behavior box in the Add-In Manager to control how and when an add-in loads in Visual Basic:
This occurs when you select an add-in for Command Line load behavior that was not declared by the author of the add-in to be "command line safe" when it was created. (This can be indicated with the Add-In Designer through a checkbox.) "Command-line safe" means that the add-in is registered in a way to indicate that it contains no user interfaces that require user input when Visual Basic is invoked through a command-line. A user interface can interfere with the operation of unattended processes (such as build scripts). If you don't indicate that an add-in is command-line safe (even if it is command-line safe), when a user selects your add-in and then Command Line in the Load Behavior box, they'll receive the warning message. This isn't a serious problem, but merely a warning to the user that the selected add-in might possibly contain UI elements that can pop up unexpectedly and halt their automated scripts by pausing for user input. Manually Setting Add-In Registry ValuesYou can also manually set the command-line safe flag (as well as the other values) for an add-in through the Windows registry.NOTE: You should not attempt to directly manipulate any Windows registry entries unless you are familiar with doing so. Setting an invalid registry entry can cause problems with Windows, even preventing you from being able to load Windows. In Visual Basic 6.0, the key that holds add-in information is located in: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Visual Basic\6.0\Addins\<add- in.name>. For Visual Basic 6.0, the LoadBehavior DWord values are:
So, to demonstrate how to use these values to indicate that a fictitious add-in (My.Addin) is command-line safe and to have it load when Visual Basic is started by command-line, you would set the following registry values, using a tool such as RegEdit: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Visual Basic\6.0\Addins\My.Addin Using the Add-In DesignerVisual Basic 6.0 includes a new tool, called the Add-In designer, to aid you in creating add-ins. To open it:
Add-In Designer: More Information About Specifying Satellite DLLWhen creating an add-in with the Add-In designer, you can specify a DLL on the Advanced tab. Be sure, however, to type only the name of the DLL file, and not its fully-qualified path. For example:MyAddinName.DLL not: Addins\MyAddinName\MyAddinName.DLL Localized Satellite DLLsIf you create a localized satellite DLL, you should also create a resources directory and a locale ID directory for the satellite DLL and install the DLL in the appropriate directory. The schematic for such a path is:<AddIn Directory>\Resources\<Locale ID>\<MySatellite.DLL> For example, a satellite DLL for the German version (Locale ID = 1031) would go into the directory: C:\Program Files\MyAddin\Resources\1031\MyAddinName.DLL REFERENCES
For additional information, please see the following articles in the
Microsoft Knowledge Base:
Q170164 : INFO: VB 6.0 Readme Part 1: Important Issues - Read First!
Keywords : kbreadme kbAddIn kbRegistry kbVBp kbVBp600 kbVS600 |
|
Last Reviewed: January 17, 2000 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |