Hi Anthony,
The size of a DLL does matter as the more the size the
more loading time will be there.
Moreover it will take that much area in Memory.
In case of MTS things change a bit because
the DLL is loaded only when you invoke a method in any of the
objects within this DLL(JIT). Moreover MTS is mainly concerned with your
objects
in the DLL and the not the DLL alone.
The rule of thumb is try to keep those objects in one DLL which
have same and/or related functionality.

What private methods are you talking about?
If a method is private in a class no one outside
this class can ever call them as they are not exposed
outside the class boundary?
Only public methods or methods of an interface
are exposed.

Regards.
Jai

-----Original Message-----
From: Anthony Burley [mailto:aburleyCAPU.NET]
Sent: Monday, June 18, 2001 5:46 AM
To: DCOMDISCUSS.MICROSOFT.COM
Subject: Does the size of the DLL Matter?

Does the size of the DLL containing MTS components impact
performance/scalability? I'm trying to figure out how best to distribute the
component classes among the dlls.

Also, what cost is there (if any) calling private methods or public
functions in
a .bas from within an MTS registered class?

----------------------------------------------------------------
Users Guide http://msdn.microsoft.com/workshop/essentials/mail.asp
contains important info. Save time, search the archives at
http://discuss.microsoft.com/archives/index.html .
To unsubscribe, mailto:DCOM-signoff-requestDISCUSS.MICROSOFT.COM

----------------------------------------------------------------
Users Guide http://msdn.microsoft.com/workshop/essentials/mail.asp
contains important info. Save time, search the archives at
http://discuss.microsoft.com/archives/index.html .
To unsubscribe, mailto:DCOM-signoff-requestDISCUSS.MICROSOFT.COM

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]