How dll size affect performance of .NET application? - 03-27-2005 , 06:07 AM
When I work on my applications (N-tier, Web or Windows)I alwaysuse typed datasets.
In the beggining i would put all typed datasets (usually 20-40)
in one project called Common(it is architecture that Microsoftuses in Duwamish solution).
So result is one dll with all Datasets in it. ONE BIG DLL.
First question? Can I split one project in more that oneassembly?
Now I put Datasets in two projects. I have Presentation datamodel with Datasets that correspond to Web or Windows form (and1 use case), and Conceptual data model with Datasets thatcorrespond usually to one table in relational database.
In the middle tier I make transformation between those Datasets.That is good solution to separate Logical and physical tier ofyour application.
So my final question? Dll containing my Datasets can be 2-3 Mblarge. How that affect my application?
Does Win exe file of ASP.NET Web form must load all dll file inmemory if it needs only one part of it?
You get my point. If it reduces performance then I shouldseparate those datasets in smaller parts.
I am working now on ASP.NET project with Access DB, and when I ambrowsing pages, somehow I got feeling that my computer alwayswork hard to display me data. And when I want Crystal Report todisplay, oh no! I have to wait half minute (but only firsttime). With Flash same thing. I have 1.8 Celeron and 256Mb RAM.
Thanks in advance
From: Igor Mitic
Posted by a user from .NET 247 (http://www.dotnet247.com/)
|Thread Tools||Search this Thread|