business logic - best practices for web app

Back in 2003 I used to separate code into a BL logic on a namespace like

CompanyName.BuisnessLogic

This code was mostly database calls

I have been out of the software industry for some time and wanted to know if this is still best practice
I read a lot about loosely coupled architecture, and was wondering what other ways there are and what I should be following
Using .net 4.5
websssAsked:
Who is Participating?
 
Miguel OzSoftware EngineerCommented:
Yes it is still in use today. In fact if you are building a new web application you are better off using ASP.NET MVC as it encourages proper separation of UI, business logic and storage (e.g. SQL database)
For tutorials in MVC check:
http://www.asp.net/mvc/tutorials/mvc-5/introduction/getting-started
http://www.asp.net/mvc/tutorials/mvc-music-store
0
 
Loganathan NatarajanLAMP DeveloperCommented:
@padas,  Ok, NP.
I was intended to help the asker to go with 3-tier architecture way to build the apps.   I was involved 3 months C# project with 3 tier architecture. So I just posted information about the idea.  Anyway, let me provide more details later when I start post an answer.
0
 
Scott Fell, EE MVEDeveloper & EE ModeratorCommented:
Loganathan Natarajan, that sounds like a good plan. Thank you.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.