Our application use a lot of graphics as embedded resources.
Application load time is 30 to 40 seconds!
Without the images it is a couple of seconds only.
Is there an optimized way of using graphics in graphics extensive
application?

The problem with using embedded resources is that they can take twice as
much memory for each image. For example, having a 100KB image as an embedded
resource gets counted once by loading the app itself and again by the new
bitmap object you create to wrap it. A way to speed up performance would be
to deploy the images as files to the file system and then load them from
there at runtime.

Another alternative is to use vector drawing, which only works if your
images break down into shape primitives nicely.

"Miron Ophir" <miron a_t mobimate d_o_t com> wrote in message
news:(E-Mail Removed)...
> Our application use a lot of graphics as embedded resources.
> Application load time is 30 to 40 seconds!
> Without the images it is a couple of seconds only.
> Is there an optimized way of using graphics in graphics extensive
> application?
>
>

Hi Miron,

Is this on SmartPhone? If so, using graphics as an embedded resource will
inflate the executable size which can lead to slow start times as the OS
performs a hash check on the file before executing it. If the executable
is also strong name signed, the CLR may perform a second hash check to
verify the strong name signature. You may consider moving the graphic
files to a separate assembly or a set of assemblies to improve performance.

Ryan Chapman
..NET Compact Framework

This posting is provided "AS IS" with no warranties, and confers no rights.