Posted by Peter Kenny-2 on Jul 14, 2004; 8:35pm
URL: https://forum.world.st/Distributing-a-prototype-Dolphin-app-tp3370977p3370986.html

"Blair McGlashan" <[hidden email]> wrote in message
news:[hidden email]...

> It is not necessary to install anything on the host machine (unless you
have
> used external components that required installation). We gave out a stack
of
> Dolphin trial CDs* at a conference some years ago that had an autorun
> executable
> on them written in Dolphin itself. DPro includes the fundamentals of this
as
> an autorun sample. I've pasted the package comment below.
>
> All of the DLLs can exist in the same directory as the deployed
executable.
> If you deploy as a ToGo executable (frankly there isn't much reason not to
> do so) then you won't even need the VM DLL - just place the C runtime
> library DLLs (MSVCRT.DLL and MSVCP60.DLL) in the root of the CD where the
> autorun exe lives. In most cases you'll get away without those because
they
> are used by so many other programs that they are almost certainly on the
> machine already, but to be sure put them on the CD because they don't take
> much room.
>
> Of course your autorun doesn't need to be a setup menu, you could launch
> directly into the executable. To do that all you'd need would be to deploy
> your application in ToGo mode, place it and the CRT DLLs on the CD, and
then
> write an autorun.inf to lauch it.
>
> Regards
>
> Blair
>
Thanks very much - that all looks very clear and simple. This information,
with the urgings of Bill and Chris above, has overcome my congenital
stinginess and persuaded me that it is now time to upgrade to Dolphin Pro. I
hope there will be no problems in transferring my program from DVE to DPro -
I presume I just file it all out as a package and install that in the DPro
image. Then, when I'm feeling more adventurous, I can explore the mysteries
of refactoring and try to tidy up the structure of what I have done.

Thanks

Peter