Package and deployment wizard

[Gerry Laenen]

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

[Steve Gerrard]

Re: Package and deployment wizard


"Gerry Laenen" <bademail@mail. be> wrote in message
news:3ffac990$0 $10600$ba620e4c @news.skynet.be ...[color=blue]
> Hi,
>
> I first created several ActiveX DLL's which interact with each other,[/color]
an SQL[color=blue]
> Server database, ... Some Active DLL's use different references: i.e.[/color]
one[color=blue]
> that does not interact with a database, does not need de ADO[/color]
reference.[color=blue]
> Above these different ActiveX DLL's, I have created another ActiveX[/color]
DLL[color=blue]
> which has references to the other compiled ActiveX DLL's. An[/color]
application is[color=blue]
> written on top of this last mentioned ActiveX DLL and it works fine on[/color]
my[color=blue]
> computer.
>
> But, when I install the application (using package and deployement) on[/color]
other[color=blue]
> computers, it does not work. The wizard does not mention anything[/color]
about[color=blue]
> references I used in compiled DLL's. Should I compile the ActiveX[/color]
DLL's with[color=blue]
> different options? Or is the package and deployment wizard not doing[/color]
his[color=blue]
> job?
>
> Thanks in advance,
>
> Gerry
>
>[/color]
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.

[CajunCoiler \(http://www.cajuncoiler.tk\)]

Re: Package and deployment wizard

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.d ll")="" 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" <bademail@mail. be> wrote in message
news:3ffac990$0 $10600$ba620e4c @news.skynet.be ...[color=blue]
> Hi,
>
> I first created several ActiveX DLL's which interact with each other, an[/color]
SQL[color=blue]
> 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[/color]
is[color=blue]
> 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[/color]
other[color=blue]
> 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[/color]
with[color=blue]
> different options? Or is the package and deployment wizard not doing his
> job?
>
> Thanks in advance,
>
> Gerry
>
>[/color]

[Bert Byfield]

Re: Package and deployment wizard

> the ActiveX DLL's with different options? Or is the package and[color=blue]
> deployment wizard not doing his job?[/color]

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.

[Gerry Laenen]

Re: Package and deployment wizard


"Steve Gerrard" <notstevegerrar d@comcast.net> schreef in bericht
news:06OdnYR79q g1aWeiRVn-vg@comcast.com. ..[color=blue]
>
> "Gerry Laenen" <bademail@mail. be> wrote in message
> news:3ffac990$0 $10600$ba620e4c @news.skynet.be ...[color=green]
> > Hi,
> >
> > I first created several ActiveX DLL's which interact with each other,[/color]
> an SQL[color=green]
> > Server database, ... Some Active DLL's use different references: i.e.[/color]
> one[color=green]
> > that does not interact with a database, does not need de ADO[/color]
> reference.[color=green]
> > Above these different ActiveX DLL's, I have created another ActiveX[/color]
> DLL[color=green]
> > which has references to the other compiled ActiveX DLL's. An[/color]
> application is[color=green]
> > written on top of this last mentioned ActiveX DLL and it works fine on[/color]
> my[color=green]
> > computer.
> >
> > But, when I install the application (using package and deployement) on[/color]
> other[color=green]
> > computers, it does not work. The wizard does not mention anything[/color]
> about[color=green]
> > references I used in compiled DLL's. Should I compile the ActiveX[/color]
> DLL's with[color=green]
> > different options? Or is the package and deployment wizard not doing[/color]
> his[color=green]
> > job?
> >
> > Thanks in advance,
> >
> > Gerry
> >
> >[/color]
> 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.
>
>[/color]

Thanks, it works fine now! This might be a very usefull tip to every VB
developer.