Lift vs CodeBehind
When comparing Lift vs CodeBehind, the Slant community recommends CodeBehind for most people. In the question“What are the best backend web frameworks?” CodeBehind is ranked 36th while Lift is ranked 58th. The most important reason people chose CodeBehind is:
CodeBehind is a modern framework with revolutionary ideas.
Ranked in these QuestionsQuestion Ranking
Pros
Pro View First architecture
Lift apparently pioneered the View First architecture, which is greatly superior to MVC for implementing DRY code. A common issue with MVC that it solves is the need to place a single component on multiple different pages, which, with MVC architecture, tends to require logic to be duplicated across multiple controllers. With View First, the code supporting the component is associated directly with the component, enabling the component to be inserted in many contexts with ease and without any additional code.
Pro Excellent security
Pro Modern
CodeBehind is a modern framework with revolutionary ideas.
Pro Code-Behind
Code-Behind pattern will be fully respected.
Pro Under .NET Core
Your project will still be under ASP.NET Core and you will benefit from all the benefits of .NET Core.
Pro Get output
You can call the output of the aspx page in another aspx page and modify its output.
Pro Modular
It is modular. Just copy the new project files, including dll and aspx, into the current active project.
Pro Simple
Developing with CodeBehind is very simple. You can use mvc pattern or model-view or controller-view or only view.
Pro Fast
The CodeBehind framework is faster than the default structure of cshtml pages in ASP.NET Core.