Last post Sep 06, 2011 02:52 PM by Lorddog
Aug 31, 2011 01:48 AM|Mani Kandan|LINK
DLL CONCEPT OR 3 TIER WHICH ONE BEST?
WHICH ONE BEST FOR USER FRIENDLY
I THINK.. VERY ADVANTAGE FOR DLL (BECAUSE THIS IS RUNTIME).,
IF ANY OTHER REPLY MEANS VERY USE FULL.
Aug 31, 2011 02:52 AM|jassi_singh|LINK
This totally depends on the complexity of the project you are going to build.
Aug 31, 2011 03:34 AM|hemant.yadav|LINK
Yes i agree with jassi..
Aug 31, 2011 03:52 AM|Slicksim|LINK
I think the importance is not to confuse what is right for the user and what is right for the development team.
Employ a strategy that suits the whole team while maintaining a highly usable front end for the customer/client.
Think about how you will feel when you come back to the project a year later, you will want to know what it is that you have done and how you can go about making changes and edits.
Personally, an N-Tier approach is the way to go, keep you DAL, BLL, PLL seperate from your view mechanism.
Aug 31, 2011 04:55 AM|shabirhakim1|LINK
I am sure That there is slight misunderstanding regarding DLL and 3 Tier .
3-Tier architecture refers to the architecture of an application that has at least 3 "logical" layers -- or parts -- that are separate. Each layer interacts with only the layer directly below, and has specific function that it is responsible for.each layer
can be in the form of DLL's .
So,How one can think of making difference between two?
Correct me if I am wrong..
Sep 06, 2011 11:50 AM|shabirhakim1|LINK
Slicksim Could you please explain me what exactly you mean by (DLL CONCEPT OR 3 TIER).I will appretiate your reply..
Sep 06, 2011 02:52 PM|Lorddog|LINK
if by DLL your meaning is to wrap up your backend .vb or .cs files into a DLL that is deployed to the server then you really need to know a few things about that. every time you update any page and deploy that new dll it should recompile and perhaps if any
user has a session they may be knocked off their session. you may not want access to your .vb or .cs files allowed to someone that has permissions to browse the files on the server. then you most definetly want to wrap them up into a dll.
typically i never do this. but if you have valid security reasons then you may want to consider it.