Lagoon issue

I was trying to deploy my first app the other night, and ended up with
an error message after all of the stripping is done.  The error was
basically: 'Dolphin cannot save the image' or something like that.

After much exploring and playing, I discovered that it was trying to
write a temporary copy of the image to a filename that conflicted with
an existing directory.

A couple of thoughts:
1) The error message was less than helpful in tracking down the cause of
the problem.  After poring over much of the deployment code I was able
to figure out what was going on.  I realize there are limited facilities
available in the stripped image at that point, but even changing the
error message to report the failure code would have helped a bit.

2) Can the temporary copy of the image be written to a unique filename
(using the Windows API for generating temporary filenames)?  It should
be possible to generate the filename before stripping so that the
facilities are available.  There is the option to keep the image when
you're done, so perhaps this isn't viable.  At the very least, adding
some extension to the name would be better I think.

Thanks,
Randy
--
Randy Coulman
NOTE: Reply-to: address is spam-guarded.  Reassemble the following to
reply directly:
rvcoulman at acm dot org

Randy,

My preference would be to generate the name up front and look for conflicts
at that point.  Anything on the back end or with conditional changes to
avoid conflicts is likely to add more confusion.  A walkback before the
image is altered should catch most problems.  Comments?

FWIW, the temporary file doesn't sound familiar.  My configured image
strippers all write to a common dedicated directory, and my installer
projects (when applicable) pick up from that point.

Have a good one,

Bill

--
Wilhelm K. Schwab, Ph.D.
[hidden email]

Bill Schwab wrote:
> Randy,
>
> My preference would be to generate the name up front and look for conflicts
> at that point.  Anything on the back end or with conditional changes to
> avoid conflicts is likely to add more confusion.  A walkback before the
> image is altered should catch most problems.  Comments?
>

That sounds good to me.

> FWIW, the temporary file doesn't sound familiar.  My configured image
> strippers all write to a common dedicated directory, and my installer
> projects (when applicable) pick up from that point.
>

If you're deploying to "Foo.EXE", it copies the EXE stub to Foo.EXE at
the beginning, strips the image, saves a snapshot to "Foo", appends that
to the EXE stub, and then (optionally) deletes Foo.

My problem was that Foo already existed as a directory.

Randy
--
Randy Coulman
NOTE: Reply-to: address is spam-guarded.  Reassemble the following to
reply directly:
rvcoulman at acm dot org

Randy,

"Randy Coulman" <[hidden email]> wrote in message
news:at8jbd$11a18r$[hidden email]...
> I was trying to deploy my first app the other night, and ended up with
> an error message after all of the stripping is done.  The error was
> basically: 'Dolphin cannot save the image' or something like that.
>
> After much exploring and playing, I discovered that it was trying to
> write a temporary copy of the image to a filename that conflicted with
> an existing directory.

Thanks. This has been recorded as issue #1101.

Best Regards,

Andy Bower
Dolphin Support
http://www.object-arts.com
---
Are you trying too hard?
http://www.object-arts.com/Relax.htm
---