CodeBehind Framework VS Nest

Elanat CMS is a large and powerful content management system based on ASP.NET Core. Elanat CMS is a CMS-Framework that does not use any of the default ASP.NET Core frameworks (Razor Pages, MVC, Blazor). Elanat CMS is built under CodeBehind Framework. Elanat CMS and CodeBehind Framework both belong to Elanat team.

When the modular name comes in ASP.NET Core, we have to use the CodeBehind framework. If you think the default MVC in ASP.NET Core has this modular feature, please leave a comment in the comments section.

About 8 months have passed since the birth of the CodeBehind framework. In these 8 months, we have released 29 new versions with revolutionary innovations, performance improvements and new features; we have now released version 2.4; CodeBehind framework version 2.4 is the 30th version of this framework.

In this article, we want to teach you how to submit form data in the CodeBehind framework. To keep it simple, we just added a View page with a Controller class and didn't use a Model.

CodeBehind Website

In this article, we discuss the disadvantages of MVC architecture in ASP.NET Core; at the same time, we compare the wonderful architecture of the CodeBehind framework with ASP.NET Core. For each disadvantage of MVC in ASP.NET Core, we will give an example and we will also add the corresponding example with the CodeBehind framework.

By studying the CodeBehind framework GitHub repository, you can get enough information about the structure of this framework and compare it with ASP.NET Core.

In this article, we want to teach you how to put these static templates into the powerful CodeBehind framework and make them dynamic.

We first explain the concept of a module, then teach how to create a module in a project built using the CodeBehind framework.

When using the NestJS framework, sometimes you may need to change some default timeout. You can define them just like you'd do in a plain Node.js HTTP server like so:

Back: a graphQL server built with Nestjs

NestJS - opinionated more scalable, but harder to learn docs

Pragmatically, we can apply this to a Nest application by creating an Interface for our services, separating the Presenter layer (Controller) from the Use Case (Services):

It’s a text document that contains all the commands a user could call to assemble an image. Let’s check an example of a Dockerfile for a nodejs app in this case it will be a NestJS app and then explain each part.

describe('Create bookmarks', () => { const dto: CreateBookmarkDto = { title: 'NestJS', link: 'https://nestjs.com/', }; it('should create bookmark', () => { return pactum .spec() .post('/bookmarks') .withHeaders({ Authorization: 'Bearer $S{userAt}', }) .withBody(dto) .expectStatus(201) .stores('bookmarkId', 'id')//store the bookmark id in the variable bookmarkId .expectBodyContains(dto.title) .expectBodyContains(dto.link) }); });

In my usual NodeJS tech stack, which includes GraphQL, NestJS, SQL (predominantly PostgreSQL with MikroORM), I encountered these limitations. To overcome them, I've developed a new stack utilizing Rust, which still offers some ease of development:

The purpose of this article is to provide a step-by-step guide for implementing authentication system in a NestJS project using the Passport middleware module.

That's exactly where I am. My manager gave me these links, that cover a lot of those words the backend uses, so I can identify what they mean and how to use them. 1. For inspiration and concepts: https://github.com/Sairyss/domain-driven-hexagon 2. Suggested to read the documentation for nest.js. They apply such concepts I don't understand: https://nestjs.com/