T
Tom
I have a main VB.NET program which instantiates a number of other VB.NET
DLLs. This DLLs all use routines from a 'base' DLL (which contains a number
of common routines); so currently I reinstantiate that 'base' DLL in every
one of my called DLLs.
The question is: Would it be better if I instantiated the 'base' DLL in the
main program, then passed a reference of the 'base' to each of my other
DLLs? Or is .NET smart enough to use same copy of the 'base' DLL when it
gets instantiated in each of my DLLs? (in other words, even though the same
'base' DLL is instantiated many times in different DLLs, VB.NET keeps only
one copy in memory of the 'base' DLL and they all share that copy).
Just wondering if going through the work of passing a reference to my 'base'
DLL is worth it.... Thanks.
Tom
DLLs. This DLLs all use routines from a 'base' DLL (which contains a number
of common routines); so currently I reinstantiate that 'base' DLL in every
one of my called DLLs.
The question is: Would it be better if I instantiated the 'base' DLL in the
main program, then passed a reference of the 'base' to each of my other
DLLs? Or is .NET smart enough to use same copy of the 'base' DLL when it
gets instantiated in each of my DLLs? (in other words, even though the same
'base' DLL is instantiated many times in different DLLs, VB.NET keeps only
one copy in memory of the 'base' DLL and they all share that copy).
Just wondering if going through the work of passing a reference to my 'base'
DLL is worth it.... Thanks.
Tom