Namespaces and projects

  • Thread starter Thread starter RickN
  • Start date Start date
R

RickN

a) Is it best to split up a large application into multiple namespaces and
multiple referenced projects or minimize the splits to all required client
code in one client dll and all required server code in one server dll?

b) To further clarify, performance-wise, is there a penalty to cross
namespace or dll boundaries when all else is equal?

Thanks,
RickN
 
RickN,

I believe that there is a slight penalty (and it is one-time, I
believe), for having code in separate assemblies (it was in a book on IL
that I was reading). However, this penalty is slight, if at all (we are
talking milliseconds here), and doesn't in any way offset the benefits of
the good organization and code reuse that you get from placing your code in
separate assemblies.

Hope this helps.
 
Hi Nicholas,

Don't forget that loading time should be slightly better when project is
split among assemblies (if all assemblies are not required at startup).

--
Miha Markic - RightHand .NET consulting & development
miha at rthand com
www.rhand.com

Nicholas Paldino said:
RickN,

I believe that there is a slight penalty (and it is one-time, I
believe), for having code in separate assemblies (it was in a book on IL
that I was reading). However, this penalty is slight, if at all (we are
talking milliseconds here), and doesn't in any way offset the benefits of
the good organization and code reuse that you get from placing your code in
separate assemblies.

Hope this helps.


--
- Nicholas Paldino [.NET/C# MVP]
- (e-mail address removed)

RickN said:
a) Is it best to split up a large application into multiple namespaces and
multiple referenced projects or minimize the splits to all required client
code in one client dll and all required server code in one server dll?

b) To further clarify, performance-wise, is there a penalty to cross
namespace or dll boundaries when all else is equal?

Thanks,
RickN
Click to expand...
Click to expand...
 
Back
Top