all groups > dotnet compact framework > october 2005 >
You're in the

dotnet compact framework

group:

What is the location of managed Dll code in memory address space


What is the location of managed Dll code in memory address space John Holmer
10/31/2005 6:17:12 AM
dotnet compact framework: I know that WinCE OS loads application code starting at address 0x00010000
and that unmanaged dlls are loaded using a modified top down search and
loaded below the address of the lowest dll of any running process, but where
are managed dlls loaded? I never see a managed dll using the WinCE Remote
Process Viewer and don't know where they load.

Also in the MSDN article "Windows CE .Net Advanced Memory Management"
article, it is stated on the Win CE platform as much code as possible should
be included in the application itself, if lack of memory address space is a
concern. Is that also true of a managed application?

Lastly, is there a way to see how much address space is used up by the code
of a managed application?

Thanks,
Re: What is the location of managed Dll code in memory address space Chris Tacke, eMVP
10/31/2005 11:33:29 AM
They're actuallyloaded by the runtime, so they don't follow the rules of
native DLLs at all.

--
Chris Tacke
Co-founder
OpenNETCF.org
Are you using the SDF? Let's do a case study.
Email us at d c s @ o p e n n e t c f . c o m
http://www.opennetcf.org/donate


[quoted text, click to view]

Re: What is the location of managed Dll code in memory address spa John Holmer
11/1/2005 6:26:05 AM
Chris, thanks for your reply. Is there a way to determine how much address
space is being reserved for the appication code by the runtime engine?

The scenario that we have is an Axim x50v that only has a maximum of 9MB of
address space available to our application, in which we load 1.5 MB of SQL
Server CE code and 1.5 MB of barcode scanner drivers. Our application is
also quite large as it allows our front-line sales partners to do many of th
activities that they typically do on our AS400s and then sync back to an SQL
DB. We had a great deal of trouble getting the scanner drivers to load
because we were out of address space. We have patched around this by having
a previous process call LoadLibrary on the driver dlls, but we don't know how
much of the remaining address space is reserved for application code and what
is used by stack and heap. We are trying to determine if our application is
on the verge of running out of space again or if we have a little breathing
room.

Thanks,
John Holmer

[quoted text, click to view]
AddThis Social Bookmark Button