Home > Archive > ASP .NET > March 2005 > Separate Project DLLs
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Separate Project DLLs
|
|
| theintrepidfox@hotmail.com 2005-03-31, 3:59 am |
|
Dear Group
Apologies for this simple question. Would be grateful if you share your
opinion on this.
I've written a web application, compiling all classes into one project
DLL. Now I wonder if there are performance / resource advantages if I
compile some classes into separate DLLs and reference them instead. Any
articles, information on this? Advantages, Di vantages? Will it slow
down the application if it has to reference a DLL?
Thanks very much for your help & efforts!
Martin
| |
| Karl Seguin 2005-03-31, 3:59 am |
| Performance isn't a factor...Divantage? You have 2+ dlls floating around
which might make it harder to maintain (assuming you are shipping a product,
which you likely aren't). Advantages? Better organization, reuse, less
bloat....
There's really no reason not to...but you shouldn't just do it for the sake
of it...hopefully there's some reasoning behind why they don't belong
together...
Karl
--
MY ASP.Net tutorials
http://www.openmymind.net/ - New and Improved (yes, the popup is annoying)
http://www.openmymind.net/faq.aspx - unofficial newsgroup FAQ (more to
come!)
<theintrepidfox@hotmail.com> wrote in message
news:1112238300.593113.237330@f14g2000cwb.googlegroups.com...
>
> Dear Group
>
> Apologies for this simple question. Would be grateful if you share your
> opinion on this.
>
> I've written a web application, compiling all classes into one project
> DLL. Now I wonder if there are performance / resource advantages if I
> compile some classes into separate DLLs and reference them instead. Any
> articles, information on this? Advantages, Divantages? Will it slow
> down the application if it has to reference a DLL?
>
> Thanks very much for your help & efforts!
>
> Martin
>
| |
| Eliyahu Goldin 2005-03-31, 4:01 pm |
| It is not a matter of performance. It is a matter of your system design. For
example, if you organize your application in presentation, business and data
access layers, you might have all forms in one project, business classes in
another project and data access classes in another project. 3 projects, 3
dlls.
Eliyahu
<theintrepidfox@hotmail.com> wrote in message
news:1112238300.593113.237330@f14g2000cwb.googlegroups.com...
>
> Dear Group
>
> Apologies for this simple question. Would be grateful if you share your
> opinion on this.
>
> I've written a web application, compiling all classes into one project
> DLL. Now I wonder if there are performance / resource advantages if I
> compile some classes into separate DLLs and reference them instead. Any
> articles, information on this? Advantages, Divantages? Will it slow
> down the application if it has to reference a DLL?
>
> Thanks very much for your help & efforts!
>
> Martin
>
|
|
|
|
|