Last post Jan 21, 2011 05:50 PM by mkubaryc
Jan 21, 2011 11:13 AM|greecemonkey|LINK
I am stuck, I got a web project that currently has about 10 projects / dlls - bll / bo / dal / baseclass etc etc.
I am writing an admin site that will run in a different domain to be the admin for the current web project.
Currently all my DAL is only SELECT and either populates the structure or a dataset.
my admin domain have the rest of the Update / Insert / Delete statements.
Is it better to make a seperate DLL / project for the admin stuff or put it in the same project at the website.
I am trying to work out if having one large DLL in a website full of functions that will never be used is better that having two DLLs one for select and one for the rest.
I dont really understand DLLs / /memory and performance
Jan 21, 2011 05:50 PM|mkubaryc|LINK
This is a loaded statment, but it sounds like you probably shouldn't worry about memory and performance at this point. That is called premature optimization.
Your DAL can and should contain all of your data access methods (the ones that perform your CRUD operations). Your DAL assembly's sole purpose is to access persistent storage so keep it simple and make sure every method does just that. You can look into
partial classes if you want to keep the "GET" methods in a separate code file than the rest of them.