Describe the difference between inline and code behind – which is best in a loosely coupled solution?
The term ‘code behind’ refers to application code that is not embedded within the ASPX page and is separated out into a separate file which is then referenced from the ASPX page. Inline code is the traditional ASP architectural model where business logic code was embedded within the ASP page. Separating the business logic code from the presentation layer offers several advantages: 1) It allows graphic designers and web developers to work on the presentation layer whilst the application developers concentrate on the business logic.2) The codebehind file is compiled as a single dll increasing the efficiency of the application3) The codebehind model offers a true OO development platform4) It speeds up development time as it allows developers to fully maximise the features of the .NET framework such as Cahing, ViewState, Session, Smart Navigation etc.5) Code is much easier to maintain and susceptible for change.6) The compiler and VS.NET provides much better support for error checking, int
Related Questions
- Some of the large Anti-Virus vendors are touting an inline solution for detecting spyware. What are the differences in the Intrusion solution and their solution?
- What is the difference between TRADITIONAL and CONTEMPORARY responses? How do I decide which is best for our organization?
- What is the difference between Training and Performance Support? What solution is best for me?
