Hi
I think u develope your application a single-tier. My advice u to use MSF
approach and split your application into assemblies. It is possible to use a
single assembly like u did. But there could be some problems. Possible
problems;
1. One day u may need to distribute your application into multiple servers.
What would you plan to do?
2. Loading a single assembly into GAC can be a problem. But when you split
it you would see total size of all your assemblies would be greater. INMH,
It is not so important.
3. One day u may need to update some functinality on any level. You should
recompile whole assembly and deploy whole assembly. Otherwise compiling and
loading related assembly would be enough.
....
Thanks,
"Joe D." <df@dgvff.compl> wrote in message
news:u4*************@TK2MSFTNGP12.phx.gbl...
Hi!
My asp.net application's DLL file is almost 5 MB. Can it be a performance
problem?
Maybe I should split it into few projects for ex. business objects
project, DAL project?
What do you think?
We have this problem - after first compilation the site runs smoothly, but
after some time it slows down, just if it was compiling itself again.
We thinks that compiling 5MB file maybe a problem here.
What do you guys think about this?
--
Joe