Where do native dlls used in p/invoke get loaded?

[Patrick Berny]

Hi there:

after reading Mike Zintel's blog about .NetCF memory management
(http://blogs.msdn.com/mikezintel/archive/2004/12/08/278153.aspx)
one thing remains unclear to me - where do native dlls that you may be
using through p/invoke get loaded? Assemblies evidently get loaded into the
1GB large allocation address space used for large allocations.

My logic tells me that they will be loaded in the usual 32MB address space
for native dlls, but I'm not completely sure. Could anyone confirm this
suspicion?

Thanks,
Patrick

 

[Brian Smith [MSFT]]

Native DLLs loaded through p/invoke are treated just like any other native
DLL in Windows CE. They are typically (but not always) loaded into the main
32MB address space. This article from MSDN has some discussion of where
DLLs go:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dncenet/htm
l/advmemmgmt.asp

Brian

--------------------

Subject: Where do native dlls used in p/invoke get loaded?
From: Patrick Berny <[email protected]>
Date: Wed, 09 Feb 2005 16:45:21 -0800

Hi there:

after reading Mike Zintel's blog about .NetCF memory management
(http://blogs.msdn.com/mikezintel/archive/2004/12/08/278153.aspx)
one thing remains unclear to me - where do native dlls that you may be
using through p/invoke get loaded? Assemblies evidently get loaded into the
1GB large allocation address space used for large allocations.

My logic tells me that they will be loaded in the usual 32MB address space
for native dlls, but I'm not completely sure. Could anyone confirm this
suspicion?

Thanks,
Patrick

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

 

[Patrick Berny]

Hi Brian:
thanks for confirming my hunch.
Patrick

briansm@nospam_microsoft.com (Brian Smith [MSFT]) wrote in