VB addin in Outlook not running on machines which don't have Visual Studio

[Moumita]

I have made a COM Outlook Addin in VB 6.0 It works perfectly fine on machines having Visaul studio but does not not run on other systems.What could be the problem.I am already including the followinf type libraries while packaging the project
MSO9.dl
MSOOUTL9.dl
ASYCFILT.dl
COMCAT.dl
MSVBVM60.dl
OLEANT32.dl
OLEPRO32.dl
STDOLE32.tl
VB6STKIT.dll

 

[Susad]

-----Original Message-----
I have made a COM Outlook Addin in VB 6.0 It works

perfectly fine on machines having Visaul studio but does
not not run on other systems.What could be the problem.I
am already including the followinf type libraries while
packaging the project;

...

Maybe you didn't build a release version of your Addin.
I'm a VC-developer and this is one of the most problem.
The Addin (or whatever) runs perfectly on machines with
Visual Studio but not on others. The problem is, in debug-
mode the binary will be linked to the debug-mode-dlls and
these doesn't exist on machines without VS.

Hope I could help
Susad

 

[Martijn Reijm]

You might give the package and deployment wizard a try; just build a Package
with it.
(Select project, choose package, choose Standard Setup and follow the rest
of the Wizard)
I've done it with a simple COM addin which reads some data from an MSAccess
database and I get the following list:
MSAdo25.tlb ADO 2.5
MSVCrt.dll
ScrRun.dll Microsoft Scripting Runtime, I use the
FileSystemObject and others
VB6StKit.dll
"VB6 Runtime and OLE automation" (no files mentioned)

And then the Setup.exe, Setup1.exe, St6Unst.Exe and my own DLL

Hope this is helpfull to you.

Martijn

I have made a COM Outlook Addin in VB 6.0 It works perfectly fine on

machines having Visaul studio but does not not run on other systems.What
could be the problem.I am already including the followinf type libraries
while packaging the project;

 

[Thomas Winter]

I have made a COM Outlook Addin in VB 6.0 It works perfectly fine on

machines having Visaul studio but does not not run on other systems.What
could be the problem.I am already including the followinf type libraries
while packaging the project;

MSO9.dll
MSOOUTL9.dll
ASYCFILT.dll
COMCAT.dll
MSVBVM60.dll
OLEANT32.dll
OLEPRO32.dll
STDOLE32.tlb
VB6STKIT.dll

FYI, you do NOT want to redistribute MSO9.DLL or MSOOUTL9.DLL/OLB. These
files are part of Microsoft Office. This is a violation of the licensing
agreement (read: illegal) for you to distribute these files. These files
will already be on a user's system of they have Microsoft Office. Your
project does reference these, but the P&D Wizard (where I assume you got
this list) doesn't know they are part of office, so it blindly tells you to
redistribute them. You have to be careful about what it tells you.

While we're on the subject, the P&D Wizard is a piece of junk. Ask any
professional VB programmer will tell you that. You would be much better off
with something like Inno Setup (www.innosetup.com). Its much more
professional and works a lot better!

-Tom