> Hi,
> I was designing an application which is intended to run in the background,
[quoted text clipped - 6 lines]
> complicates the code slightly.
> Thanks for your help.
I presume you are talking about some stream resources, as string and other
such resources are pretty minimal. If you are worried about the memory
footprint, I wouldn't use the dll to embeded resources. If you feel a need
to embed the resource, then my preference is always to embed it in the dll
that needs it. If you need the resource in multiple dlls, then I would
strongly consider installing to the disk.
Reuben - 10 Mar 2008 00:40 GMT
Sorry if I caused some confusion, but I was asking if the entire DLL is
loaded into memory when the exe is loaded. The exe appears to load its entire
contents, and I was hoping to reduce the footprint by storing images, etc. in
a DLL, which would hopefully only be loaded into memory when needed.
Family Tree Mike - 10 Mar 2008 03:11 GMT
> Sorry if I caused some confusion, but I was asking if the entire DLL is
> loaded into memory when the exe is loaded. The exe appears to load its entire
> contents, and I was hoping to reduce the footprint by storing images, etc. in
> a DLL, which would hopefully only be loaded into memory when needed.
DLL's are loaded as needed, or, if explicitly loaded by
Assembly.LoadFromFile(). Unloading a dll when you are finished is not as
easy, from what I have heard. If this is an issue, you may want to ask
others about that.