468,719 Members | 1,854 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 468,719 developers. It's quick & easy.

Package and deployment wizard

Hi,

I first created several ActiveX DLL's which interact with each other, an SQL
Server database, ... Some Active DLL's use different references: i.e. one
that does not interact with a database, does not need de ADO reference.
Above these different ActiveX DLL's, I have created another ActiveX DLL
which has references to the other compiled ActiveX DLL's. An application is
written on top of this last mentioned ActiveX DLL and it works fine on my
computer.

But, when I install the application (using package and deployement) on other
computers, it does not work. The wizard does not mention anything about
references I used in compiled DLL's. Should I compile the ActiveX DLL's with
different options? Or is the package and deployment wizard not doing his
job?

Thanks in advance,

Gerry
Jul 17 '05 #1
4 5282

"Gerry Laenen" <ba******@mail.be> wrote in message
news:3f***********************@news.skynet.be...
Hi,

I first created several ActiveX DLL's which interact with each other, an SQL Server database, ... Some Active DLL's use different references: i.e. one that does not interact with a database, does not need de ADO reference. Above these different ActiveX DLL's, I have created another ActiveX DLL which has references to the other compiled ActiveX DLL's. An application is written on top of this last mentioned ActiveX DLL and it works fine on my computer.

But, when I install the application (using package and deployement) on other computers, it does not work. The wizard does not mention anything about references I used in compiled DLL's. Should I compile the ActiveX DLL's with different options? Or is the package and deployment wizard not doing his job?

Thanks in advance,

Gerry

There is an option in P & D Wizard to make a dependency file. I would do
this on each of the ActiveX Dlls first, starting with the lowest tier.
Then when you make a setup for the main app, it "should" recognize those
dependencies, and include any needed support files.
Jul 17 '05 #2
Take note of which of your DLLs are missing on the other system, and just
manually add them to the inclusion list when you package the project.

Or, you may want to consider embedding the DLLs into the program, to
where your main form's load event tests for it's existance, and if it's not
there, create it, as in...

If Dir("c:\windows\system\MyDLL.dll")="" Then
Call CreateMyDll( )
End If

I use a similar method for embedding small icons, wavs, midis, pointers,
and such, where resource files are infeasable.
---
C.L. Mayeux
Owner, MSB Data Systems
http://www.msbdatasystems.com

"Gerry Laenen" <ba******@mail.be> wrote in message
news:3f***********************@news.skynet.be...
Hi,

I first created several ActiveX DLL's which interact with each other, an SQL Server database, ... Some Active DLL's use different references: i.e. one
that does not interact with a database, does not need de ADO reference.
Above these different ActiveX DLL's, I have created another ActiveX DLL
which has references to the other compiled ActiveX DLL's. An application is written on top of this last mentioned ActiveX DLL and it works fine on my
computer.

But, when I install the application (using package and deployement) on other computers, it does not work. The wizard does not mention anything about
references I used in compiled DLL's. Should I compile the ActiveX DLL's with different options? Or is the package and deployment wizard not doing his
job?

Thanks in advance,

Gerry

Jul 17 '05 #3
> the ActiveX DLL's with different options? Or is the package and
deployment wizard not doing his job?


The Packand and Deployment Wizard is not doing his job. Get a third party
install program (some are free, some are expensive, all work better than
PDW).
Also, the source for PDW is included with VB6 so you can debug it
yourself, if you want to choose that path. MicroSoft skipped that step.


Jul 17 '05 #4

"Steve Gerrard" <no*************@comcast.net> schreef in bericht
news:06********************@comcast.com...

"Gerry Laenen" <ba******@mail.be> wrote in message
news:3f***********************@news.skynet.be...
Hi,

I first created several ActiveX DLL's which interact with each other,

an SQL
Server database, ... Some Active DLL's use different references: i.e.

one
that does not interact with a database, does not need de ADO

reference.
Above these different ActiveX DLL's, I have created another ActiveX

DLL
which has references to the other compiled ActiveX DLL's. An

application is
written on top of this last mentioned ActiveX DLL and it works fine on

my
computer.

But, when I install the application (using package and deployement) on

other
computers, it does not work. The wizard does not mention anything

about
references I used in compiled DLL's. Should I compile the ActiveX

DLL's with
different options? Or is the package and deployment wizard not doing

his
job?

Thanks in advance,

Gerry

There is an option in P & D Wizard to make a dependency file. I would do
this on each of the ActiveX Dlls first, starting with the lowest tier.
Then when you make a setup for the main app, it "should" recognize those
dependencies, and include any needed support files.


Thanks, it works fine now! This might be a very usefull tip to every VB
developer.
Jul 17 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

4 posts views Thread by chris | last post: by
1 post views Thread by CARIGAR | last post: by
reply views Thread by zhoujie | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.