architecture for .Net web applications, plz guide me‏

Question

User852864959 posted

Thanks for your attention and time,

Please guide me what can be the best application architecture for small/ mediaum asp.net application.


My considerations are:


1. Easy management and modification

2. Code Re-usability

3. Time safety (rapid development)

4. Easy testing and deployment


Please consider below mention architecture, I will thankful to you for your comments and feedback.


 A empty Solotion which have the following projects in it.


1. A Web (UI)
2. A Class Library (Application Controller) UI will communicate will other projects and classes through it and not directly.
3. A Class Library (Customer types/ business objects)
4. A Class Library (Business Logic)
5. A Class Library (Common Library) It will be used in multiple projects.

Please guide is there any better way to do this ? Will we call above mention layered architecture or it has some other name ?

Answer 1

User1911587250 posted

I think a Data Acces Layer (DAL) should  be considered .

Answer 2

User852864959 posted

I think a Data Acces Layer (DAL) should  be considered .

Thanks for taking care Ali,

can you please explain what is your suggestion in this regard ?

thanks

 

Answer 3

User1911587250 posted

a traditional leyar in enterprise projects is DAL .

DAL is a abstract layer between your datasource(usually relattional database) and you application.

there are several ways to gain this level of abstraction but the traditional way is to use an ORM tool .

so you can choose a ORM tool ( LINQ2SQL Nhibernate or Entity Framework and more) to create classes over you database tables an put these classes in another project in your solution and add a reference to it from you mani WebUI project .

this way when your DB changes only your DAL classes changes and you can complie just this project when a changing in DB occurs.

hope this helps.

Answer 4

User-389939489 posted

> the traditional way is to use an ORM tool

That is not traditional, it's happened during the last 10 years or so. A traditional approach is expose stored procedures and access them from your application code (possibly with a DAL) through something like the DAAB. Note that the difference is not only in that with an ORM you are implying an object model, but even more that in a traditional approach there is not such a notion as CRUD: i.e., the database is a self-standing component, not just a flat storage medium.

Kind regards,

-LV

Answer 5

User1911587250 posted

by "traditional" I meant "usual" sorry for my bad English if this the case and thanks for your attention.

Answer 6

User-389939489 posted

> by "traditional" I meant "usual"

Well, I'd contend even that: there is not only e-commerce applications.

> sorry for my bad English if this the case and thanks for your attention

No problem, and you are welcome.

-LV

Answer 7

User-1067358373 posted

Check the link below.

Imar guides you in developing a n-layered asp.net application.

http://imar.spaanjaars.com/QuickDocId.aspx?quickdoc=416