CodeBehind is a modern back-end framework under ASP.NET Core. CodeBehind was developed by Elanat in 2023 and competes with Microsoft's default web frameworks (ASP.NET Core MVC and Razor Pages and Blazor). CodeBehind is an engineering masterpiece that simultaneously provides the possibility of development based on MVC, Model-View, Controller-View, only View and Web-Forms. The type of structure and naming in CodeBehind is a nostalgia that reminds of former Microsoft Web-Forms.
The aspx extension is the files of the view section in the CodeBehind framework and they supports standard syntax (<%=Standard%>) and Razor syntax (@Razor). This framework guarantees the separation of server-side codes from the design part (html) and there is no need to write server-side codes in the view.
Code Behind framework inherits every advantage of ASP.NET Core and gives it more simplicity, power, flexibility and has high serverside independence.
CodeBehind framework is an alternative to ASP.NET Core.
- Fast: The CodeBehind framework is faster than Microsoft's default web frameworks (ASP.NET Core MVC and Razor Pages).
- Simple: Developing with CodeBehind is very simple. You can use MVC pattern or Model-View or Controller-View or only View.
- Modular: It is modular. Just copy the new project files, including DLL and aspx, into the current published project (plug and play).
- Get output: You can call the output of the aspx page in another aspx page and modify its output.
- Under .NET Core: Your project will still be under ASP.NET Core and you will benefit from all the benefits of .NET Core.
- Code-Behind: Code-Behind pattern will be fully respected.
- Modern: CodeBehind is a modern framework with revolutionary ideas.
- Understandable: View is preferable to Controller and there is no need to set Controllers in route.
- Adaptable: The CodeBehind framework can even be used with Razor Pages and ASP.NET Core MVC.
- Loose coupling: The different components of CodeBehind work independently of each other.
- RAD: Everything is automated in CodeBehind framework, just focus on development.
- WebForms Core technology: Supports a new and unique approach modeled after Microsoft's former WebForms.
CodeBehind is .NET Diamond!
In every scenario, CodeBehind performs better than the default structure in ASP.NET Core.
View section: aspx page (razor syntax)
@page
@{
Random rand = new Random();
}
<div>
<h1>Random value: @rand.Next(1000000)</h1>
</div>View section: aspx page (standard syntax)
<%@ Page %>
<%
Random rand = new Random();
%>
<div>
<h1>Random value: <%=rand.Next(1000000)%></h1>
</div>View File: Default.aspx (razor syntax)
@page
@controller MyController
@model MyModel
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8" />
<title>@model.PageTitle</title>
</head>
<body>
@model.BodyValue
</body>
</html>View File: Default.aspx (standard syntax)
<%@ Page Controller="MyController" Model="MyModel" %>
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8" />
<title><%=model.PageTitle%></title>
</head>
<body>
<%=model.BodyValue%>
</body>
</html>Model File: Default.aspx.Model.cs
using CodeBehind;
public partial class MyModel : CodeBehindModel
{
public string PageTitle { get; set; }
public string BodyValue { get; set; }
}Controller File: Default.aspx.Controller.cs
using CodeBehind;
public partial class MyController : CodeBehindController
{
public void PageLoad(HttpContext context)
{
MyModel model = new MyModel();
model.PageTitle = "My Title";
model.BodyValue = "HTML Body";
View(model);
}
}Program File: Program.cs
var builder = WebApplication.CreateBuilder(args);
var app = builder.Build();
SetCodeBehind.CodeBehindCompiler.Initialization();
app.UseCodeBehind();
app.Run();- Simple and structured MVC in CodeBehind
- It is not necessary to follow the MVC pattern
- Load aspx page finally result in another aspx page
- Examples of development
- Send data
- Web part in CodeBehind
- Razor syntax reference for CodeBehind framework
- Standard syntax reference for CodeBehind framework
- Constructor method
- HtmlData classes
- Template
- Transfer template block data in ViewData
- Layout
- Section
- Error handling
- Options
- Namespace and DLL for CodeBehind view class
- Manage roles in CodeBehind (Authentication and Authorization)
- Use cache
- Controller class constructor and Model class constructor
- Using Web-Forms
- Error detection
- How to use CodeBehind?
- Route configuration
- Used with Razor Pages and ASP.NET Core MVC
- Modularity in the default mode
- Modularity in the configuration of the controller in the route
- New features on new versions
- How is the list of views finally made?
- CodeBehind framework data
- MVC architecture in CodeBehind
- Performance test, ASP.NET Core MVC and Razor Pages vs CodeBehind Framework in version 2.2
- Performance test in only view section in version 1.5.2 (ASP.NET Core VS CodeBehind)
- CodeBehind story
- ASP.NET Core VS CodeBehind; why should we use CodeBehind?
- CodeBehind framework vs Code-Behind pattern
- How to create modular systems by CodeBehind framework?
- How to create scheduled task system by CodeBehind framework?
- How to create startup system by CodeBehind framework?
- How to create dynamic middleware system by CodeBehind framework?
- Video 1- Hello World!
- Video 2- Set dynamic header
- Video 3- Page list in default page
- Video 4- How to use CodeBehind framework?
- Video 5- Advanced programming with return template
- Video 6- Using WebForms Core
Get from Elanat website:
https://elanat.net/category/download_code_behind/
Get from GitHub:
https://github.com/elanatframework/Code_behind/releases
Get from Nuget (We added CodeBehind in Nuget so that you can access it easily):