Size of Common Assembly

[The Great Pawn Hunter]

Hi everyone,

I am a newbie to this group and have a general question. What size
assembly is a good size for putting common objects and their methods
into so as not to have too much overhead when calling one object. I
understand that it depends on the amount of memory in the computer. I
heard that the rest of the assembly is also loaded into memory with
the one object that was instantiated. Is that true? If so then how
many objects would you recommend to put into an assembly to keep the
size down? With one method having around 50 lines of code and an
object having around 5 methods. Is there already a design for
organizing a central common reusable assembly out there? If so what
are the general rules of thumb?

The Great Pawn Hunter

[Kevin Spencer]

You can put an awful lot into a single assembly. Check out the mscorlib
assembly in your Visual Studio object browser.

--
HTH,

Kevin Spencer
Microsoft MVP

Printing Components, Email Components,
FTP Client Classes, Enhanced Data Controls, much more.
DSI PrintManager, Miradyne Component Libraries:
http://www.miradyne.net

"The Great Pawn Hunter" <ma********@aol.comwrote in message
news:11**********************@w5g2000hsg.googlegro ups.com...

Hi everyone,

I am a newbie to this group and have a general question. What size
assembly is a good size for putting common objects and their methods
into so as not to have too much overhead when calling one object. I
understand that it depends on the amount of memory in the computer. I
heard that the rest of the assembly is also loaded into memory with
the one object that was instantiated. Is that true? If so then how
many objects would you recommend to put into an assembly to keep the
size down? With one method having around 50 lines of code and an
object having around 5 methods. Is there already a design for
organizing a central common reusable assembly out there? If so what
are the general rules of thumb?

The Great Pawn Hunter