Hello Peter
From your post, my understanding on this issue is: you wonder how to
distribute a Office COM Add-in created with Visual Basic 6.0. If I'm off
base, please feel free to let me know.
When VB Addin designer compile the automation addin and build the DLL, it
automatically register the DLL for us. The registry subkey is
\HKEY_CURRENT_USER\Software\Microsoft\Office\appname\AddIns. The
*Description* entry is your setting for the *Addin Description* option in
the add-in designer. The *FriendlyName* entry is your setting for the
*Addin Display name* option in the designer.
(
http://msdn2.microsoft.com/en-us/library/aa155767(office.10).aspx) Add-ins
that are registered under HKEY_CURRENT_USER apply to that user only;
Add-ins that are registered under HEY_LOCAL_MACHINE are global to the
system and load for all instances of that application
(
http://msdn2.microsoft.com/en-us/library/aa155767(office.10).aspx). The VB
add-in designer is written to build per-user add-ins. If it is to be built
for all the users, see:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;290868
Now, for your question about how to distribute a Office COM Add-in created
with Visual Basic 6.0, please refer to the MSDN article:
http://msdn2.microsoft.com/en-us/library/aa140987(office.10).aspx
According to the article, the easiest way to distribute a COM add-in is to
include the add-in designer in the Add-in project and then create a setup
program for the add-in. The user can install and register the add-in by
running the setup program. To create the setup program, run the Visual
Basic 6.0 Package and Deployment Wizard on the Add-in project. When the
user runs the setup program, all the files required for the add-in to run
will be copied to the user's computer and registered. As for the Visual
Basic 6.0 Package and Deployment Wizard, here are some related articles for
your reference:
Get Started with the Package and Deployment Wizard (PDW)
http://support.microsoft.com/default.aspx?scid=/support/vbasic/gettingstarte
d/pdw.asp&SD=MSDN
Best practices for deploying Visual Basic 6.0 applications
http://support.microsoft.com/kb/830761
Frequently asked questions about the Package and Deployment Wizard in
Visual Basic 6.0
http://support.microsoft.com/kb/885484
Last but not least, I hope to let you know that Visual Basic 6 is currently
in its Extended Phase support. According to
http://msdn2.microsoft.com/en-us/vbrun/ms788707.aspx, Visual Basic 6.0 will
no longer be supported starting March 2008.
If you have any other concern or need anything else, please feel free to
let me know.
Sincerely,
Jialiang Ge (
[email protected], remove 'online.')
Microsoft Online Community Support
==================================================
For MSDN subscribers whose posts are left unanswered, please check this
document:
http://blogs.msdn.com/msdnts/pages/postingAlias.aspx
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications. If you are using Outlook Express/Windows Mail, please make sure
you clear the check box "Tools/Options/Read: Get 300 headers at a time" to
see your reply promptly.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
