Using D6, deploy app with runtime packages..package collections editor?

#1 08-05-2008, 08:37 PM

I have an app that has been growing quite large as a single exe. Most of
the runtime packages NEVER change. There are about 15 runtime packages
that would need to be include with the app. This means 15 "dangling"
packages in the application folder. It looks like the package collection
editor will combine them all into a "dpc" file. This is a single six meg
file, which seems to be exactly what I want, but how does my app use this
file since the "build with runtime packages" only supports DCP... that's DCP
files, not DPC files.

Thanks
Jim

#2 08-05-2008, 09:17 PM

Jim wrote:
> I have an app that has been growing quite large as a single exe. Most of
> the runtime packages NEVER change. There are about 15 runtime packages
> that would need to be include with the app. This means 15 "dangling"
> packages in the application folder.

I don't understand what you mean by "dangling."

> It looks like the package collection
> editor will combine them all into a "dpc" file. This is a single six meg
> file, which seems to be exactly what I want,

Why does it seem that way?

> but how does my app use this
> file since the "build with runtime packages" only supports DCP... that's DCP
> files, not DPC files.

A package collection has the files needed for other developers to use
the package. It is not a "superpackage."

You can't combine packages. You can make new packages, though. Make a
new package and put in it all the units that are in the packages that
you'd like to combine. Now, make your EXE use that single package
instead of all the other run-time packages. (You don't need to change
the design-time packages. They'll continue using the old run-time packages.)

--
Rob

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode