Pushing it to a single tier would likely gain nothing in memory usage. It's
also not true that you have a 32MB hard limit. The CF does a lot of
allocation from shared space. You have a 32MB virtual space limit per
process.
-Chris
Surely if an app is the first (or perhaps only) .NET app on the device,
the CF would be using that app's memory space for the framework, or does
the CF somehow create it's own process along side your own to run in?
> Pushing it to a single tier would likely gain nothing in memory usage. It's
> also not true that you have a 32MB hard limit. The CF does a lot of
[quoted text clipped - 20 lines]
>> If we squished the number of layers from 4 down to 2 (GUI & "Everything
>> else"), would this help things memory-wise?
<ctacke/> - 03 Apr 2006 16:30 GMT
The CF runs partly in slot 0, partly in slot 1 and partly in shared memory
space. Read all 3 parts of this, along with Mike Zintel's linked blog
entry:
http://blogs.msdn.com/stevenpr/archive/2005/12/14/503818.aspx
-Chris
> Surely if an app is the first (or perhaps only) .NET app on the device,
> the CF would be using that app's memory space for the framework, or does
[quoted text clipped - 24 lines]
>>> If we squished the number of layers from 4 down to 2 (GUI & "Everything
>>> else"), would this help things memory-wise?
Jon Brunson - 03 Apr 2006 17:06 GMT
Thanks Chris
> The CF runs partly in slot 0, partly in slot 1 and partly in shared memory
> space. Read all 3 parts of this, along with Mike Zintel's linked blog
[quoted text clipped - 32 lines]
>>>> If we squished the number of layers from 4 down to 2 (GUI & "Everything
>>>> else"), would this help things memory-wise?