diff --git a/Directory.Packages.props b/Directory.Packages.props
index df44503ee8..0a7d88c504 100644
--- a/Directory.Packages.props
+++ b/Directory.Packages.props
@@ -11,18 +11,19 @@
-
+
+
-
-
-
-
+
+
+
+
@@ -53,67 +54,66 @@
-
+
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
-
-
-
+
+
+
-
+
-
-
-
-
-
-
-
-
-
-
-
+
+
+
+
+
+
+
+
+
+
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
@@ -122,21 +122,21 @@
-
+
-
+
-
-
-
-
-
+
+
+
+
+
@@ -149,7 +149,7 @@
-
+
@@ -168,17 +168,18 @@
-
-
+
+
-
+
+
-
-
-
+
+
+
@@ -193,6 +194,6 @@
-
+
-
+
\ No newline at end of file
diff --git a/README.md b/README.md
index fa6632daa8..4ef4bfab56 100644
--- a/README.md
+++ b/README.md
@@ -14,6 +14,7 @@
- [Quick Start](https://abp.io/docs/latest/tutorials/todo) is a single-part, quick-start tutorial to build a simple application with the ABP Framework. Start with this tutorial if you want to understand how ABP works quickly.
- [Web Application Development Tutorial](https://abp.io/docs/latest/tutorials/book-store) is a complete tutorial on developing a full-stack web application with all aspects of a real-life solution.
- [Modular Monolith Application](https://abp.io/docs/latest/tutorials/modular-crm/index): A multi-part tutorial that demonstrates how to create application modules, compose and communicate them to build a monolith modular web application.
+- [Microservice Tutorial](https://abp.io/docs/latest/tutorials/microservice/index): A multi-part guide that walks you through building a microservice solution with ABP, from creating independent services and enabling inter-service communication to exposing them through an API Gateway and generating CRUD pages with ABP Suite.
## What ABP Provides?
diff --git a/abp_io/AbpIoLocalization/AbpIoLocalization/Admin/Localization/Resources/en.json b/abp_io/AbpIoLocalization/AbpIoLocalization/Admin/Localization/Resources/en.json
index 7a9687e6d0..7f9b928749 100644
--- a/abp_io/AbpIoLocalization/AbpIoLocalization/Admin/Localization/Resources/en.json
+++ b/abp_io/AbpIoLocalization/AbpIoLocalization/Admin/Localization/Resources/en.json
@@ -672,6 +672,7 @@
"SupportQuestionCountPerDeveloperOnRenewLicense": "Support Question Count Per Developer for License Renewal",
"SupportQuestionCountPerDeveloperOnNewLicense": "Support Question Count Per Developer for New License",
"IncludedDeveloperCount": "Included Developer Count",
+ "AiTokenCountPerDeveloper": "AI Token Count Per Developer",
"CanBuyAdditionalDevelopers": "Can Buy Additional Developers",
"HasEmailSupport": "Has Email Support",
"IsSupportPrivateQuestion": "Can Open Private Support Question",
diff --git a/abp_io/AbpIoLocalization/AbpIoLocalization/Base/Localization/Resources/en.json b/abp_io/AbpIoLocalization/AbpIoLocalization/Base/Localization/Resources/en.json
index 35c4766f8b..622f30420c 100644
--- a/abp_io/AbpIoLocalization/AbpIoLocalization/Base/Localization/Resources/en.json
+++ b/abp_io/AbpIoLocalization/AbpIoLocalization/Base/Localization/Resources/en.json
@@ -228,7 +228,9 @@
"Articles": "Articles",
"Organizations": "Organizations",
"ManageAccount": "Manage Account",
+ "MyManageAccount": "My Account",
"CommunityProfile": "Community Profile",
+ "MyCommunityProfile": "My Community Profile",
"BlogProfile": "Blog Profile",
"Tickets": "Tickets",
"Raffles": "Raffles",
@@ -248,13 +250,28 @@
"NewsletterDefinition": "Blog posts, community news, etc.",
"OrganizationOverview": "Organization Overview",
"EmailPreferences": "Email Preferences",
+ "MyEmailPreferences": "My Email Preferences",
"VideoCourses": "Essential Videos",
"DoYouAgreePrivacyPolicy": "By clicking Subscribe button you agree to the Terms & Conditions and Privacy Policy.",
"AbpConferenceDescription": "ABP Conference is a virtual event for .NET developers to learn and connect with the community.",
"Mobile": "Mobile",
"MetaTwitterCard": "summary_large_image",
"IPAddress": "IP Address",
+ "MyReferrals": "My Referrals",
"LicenseBanner:InfoText": "Your license will expire in {0} days.",
- "LicenseBanner:CallToAction": "Please extend your license."
+ "LicenseBanner:CallToAction": "Please extend your license.",
+ "Referral.CreatorUserIdIsRequired": "Creator user ID is required.",
+ "Referral.TargetEmailIsRequired": "Target email is required.",
+ "Referral.YouAlreadyHaveLinkForThisEmail": "You have already created a referral link for this email address.",
+ "Referral.MaxLinkLimitExceeded": "You have reached the maximum limit of {Limit} active referral links.",
+ "Referral.LinkNotFound": "Referral link not found.",
+ "Referral.LinkNotFoundOrNotOwned": "Referral link not found or you don't have permission to access it.",
+ "Referral.CannotDeleteUsedLink": "You cannot delete a referral link that has already been used.",
+ "Referral.CannotReferYourself": "You cannot create a referral link for your own email address.",
+ "Referral:TargetEmail": "Target Email",
+ "Referral.CannotReferSameOrganizationMember": "You cannot create a referral link for a user who is already a member of your organization.",
+ "LinkCopiedToClipboard": "Link copied to clipboard",
+ "AreYouSureToDeleteReferralLink": "Are you sure you want to delete this referral link?",
+ "DefaultErrorMessage": "An error occurred."
}
}
\ No newline at end of file
diff --git a/abp_io/AbpIoLocalization/AbpIoLocalization/Www/Localization/Resources/en.json b/abp_io/AbpIoLocalization/AbpIoLocalization/Www/Localization/Resources/en.json
index 18730b51d6..981500451a 100644
--- a/abp_io/AbpIoLocalization/AbpIoLocalization/Www/Localization/Resources/en.json
+++ b/abp_io/AbpIoLocalization/AbpIoLocalization/Www/Localization/Resources/en.json
@@ -1553,6 +1553,15 @@
"IntegrateToYourKubernetesCluster_Description1": "Connect your local development environment to a local or remote Kubernetes cluster, where that cluster already runs your microservice solution.",
"IntegrateToYourKubernetesCluster_Description2": "Access any service in Kubernetes with their service name as DNS, just like they are running in your local computer.",
"IntegrateToYourKubernetesCluster_Description3": "Intercept any service in that cluster, so all the traffic to the intercepted service is automatically redirected to your service that is running in your local machine. When your service needs to use any service in Kubernetes, the traffic is redirected back to the cluster, just like your local service is running inside the Kubernetes.",
+ "AskOurAiAssistant": "Ask Our AI Assistant",
+ "AskOurAiAssistant_Description1": "Build faster with an AI that actually understands your ABP project. The ABP AI Assistant answers your technical questions, explains your code, and helps you solve problems directly inside ABP Studio — with full awareness of your project’s structure. You can even send screenshots or code files to get precise, context-based guidance.",
+ "AskOurAiAssistant_Description2": "What It Helps You Do",
+ "AskOurAiAssistant_Description3": "Ask anything about your ABP project — domain layer, modules, configuration, entities, services, or UI.",
+ "AskOurAiAssistant_Description4": "Get smart, code-aware explanations tailored to your solution.",
+ "AskOurAiAssistant_Description5": "Generate snippets and scaffolding suggestions instantly.",
+ "AskOurAiAssistant_Description6": "Fix errors faster with context-aware debugging support.",
+ "AskOurAiAssistant_Description7": "Learn ABP best practices as you build.",
+ "AskOurAiAssistant_Description8": "Whether you're generating new features, debugging an issue, or exploring a module, the AI Assistant gives you actionable, project-specific answers — right when you need them.",
"GetInformed": "Get Informed",
"Studio_GetInformed_Description1": "Leave your contact information to get informed and try it first when ABP Studio has been launched.",
"Studio_GetInformed_Description2": "Planned preview release date: Q3 of 2023.",
diff --git a/common.props b/common.props
index 82d1e8abbf..42e230791c 100644
--- a/common.props
+++ b/common.props
@@ -18,11 +18,6 @@
-
-
-
-
- all
diff --git a/docs/en/Blog-Posts/2025-08-08 v10_0_Release_Stable/POST.md b/docs/en/Blog-Posts/2025-08-08 v10_0_Release_Stable/POST.md
new file mode 100644
index 0000000000..32647b5b6c
--- /dev/null
+++ b/docs/en/Blog-Posts/2025-08-08 v10_0_Release_Stable/POST.md
@@ -0,0 +1,89 @@
+# ABP.IO Platform 10.0 Final Has Been Released!
+
+We are glad to announce that [ABP](https://abp.io/) 10.0 stable version has been released today.
+
+## What's New With Version 10.0?
+
+All the new features were explained in detail in the [10.0 RC Announcement Post](https://abp.io/community/announcements/announcing-abp-10-0-release-candidate-86lrnyox), so there is no need to review them again. You can check it out for more details.
+
+## Getting Started with 10.0
+
+### How to Upgrade an Existing Solution
+
+You can upgrade your existing solutions with either ABP Studio or ABP CLI. In the following sections, both approaches are explained:
+
+### Upgrading via ABP Studio
+
+If you are already using the ABP Studio, you can upgrade it to the latest version. ABP Studio periodically checks for updates in the background, and when a new version of ABP Studio is available, you will be notified through a modal. Then, you can update it by confirming the opened modal. See [the documentation](https://abp.io/docs/latest/studio/installation#upgrading) for more info.
+
+After upgrading the ABP Studio, then you can open your solution in the application, and simply click the **Upgrade ABP Packages** action button to instantly upgrade your solution:
+
+
+
+### Upgrading via ABP CLI
+
+Alternatively, you can upgrade your existing solution via ABP CLI. First, you need to install the ABP CLI or upgrade it to the latest version.
+
+If you haven't installed it yet, you can run the following command:
+
+```bash
+dotnet tool install -g Volo.Abp.Studio.Cli
+```
+
+Or to update the existing CLI, you can run the following command:
+
+```bash
+dotnet tool update -g Volo.Abp.Studio.Cli
+```
+
+After installing/updating the ABP CLI, you can use the [`update` command](https://abp.io/docs/latest/CLI#update) to update all the ABP related NuGet and NPM packages in your solution as follows:
+
+```bash
+abp update
+```
+
+You can run this command in the root folder of your solution to update all ABP related packages.
+
+## Migration Guides
+
+There are a few breaking changes in this version that may affect your application. Please read the migration guide carefully, if you are upgrading from v9.x: [ABP Version 10.0 Migration Guide](https://abp.io/docs/10.0/release-info/migration-guides/abp-10-0)
+
+## Community News
+
+### New ABP Community Articles
+
+As always, exciting articles have been contributed by the ABP community. I will highlight some of them here:
+
+* [Alper Ebiçoğlu](https://abp.io/community/members/alper)
+ * [Optimize your .NET app for production Part 1](https://abp.io/community/articles/optimize-your-dotnet-app-for-production-for-any-.net-app-wa24j28e)
+ * [Optimize your .NET app for production Part 2](https://abp.io/community/articles/optimize-your-dotnet-app-for-production-for-any-.net-app-2-78xgncpi)
+ * [Return Code vs Exceptions: Which One is Better?](https://abp.io/community/articles/return-code-vs-exceptions-which-one-is-better-1rwcu9yi)
+* [Sumeyye Kurtulus](https://abp.io/community/members/sumeyye.kurtulus)
+ * [Building Scalable Angular Apps with Reusable UI Components](https://abp.io/community/articles/building-scalable-angular-apps-with-reusable-ui-components-b9npiff3)
+ * [Angular Library Linking Made Easy: Paths, Workspaces and Symlinks](https://abp.io/community/articles/angular-library-linking-made-easy-paths-workspaces-and-5z2ate6e)
+* [erdem çaygör](https://abp.io/community/members/erdem.caygor)
+ * [Building Dynamic Forms in Angular for Enterprise](https://abp.io/community/articles/building-dynamic-forms-in-angular-for-enterprise-6r3ewpxt)
+ * [From Server to Browser: Angular TransferState Explained](https://abp.io/community/articles/from-server-to-browser-angular-transferstate-explained-m99zf8oh)
+* [Mansur Besleney](https://abp.io/community/members/mansur.besleney)
+ * [Top 10 Exception Handling Mistakes in .NET](https://abp.io/community/articles/top-10-exception-handling-mistakes-in-net-jhm8wzvg)
+* [Berkan Şaşmaz](https://abp.io/community/members/berkansasmaz)
+ * [How to Dynamically Set the Connection String in EF Core](https://abp.io/community/articles/how-to-dynamically-set-the-connection-string-in-ef-core-30k87fpj)
+* [Oğuzhan Ağır](https://abp.io/community/members/oguzhan.agir)
+ * [The ASP.NET Core Dependency Injection System](https://abp.io/community/articles/the-asp.net-core-dependency-injection-system-3vbsdhq8)
+* [Selman Koç](https://abp.io/community/members/selmankoc)
+ * [5 Things Keep in Mind When Deploying Clustered Environment](https://abp.io/community/articles/5-things-keep-in-mind-when-deploying-clustered-environment-i9byusnv)
+* [Muhammet Ali ÖZKAYA](https://abp.io/community/members/m.aliozkaya)
+ * [Repository Pattern in ASP.NET Core](https://abp.io/community/articles/repository-pattern-in-asp.net-core-2dudlg3j)
+* [Armağan Ünlü](https://abp.io/community/members/armagan)
+ * [UI/UX Trends That Will Shape 2026](https://abp.io/community/articles/UI-UX-Trends-That-Will-Shape-2026-bx4c2kow)
+* [Salih](https://abp.io/community/members/salih)
+ * [What is That Domain Service in DDD for .NET Developers?](https://abp.io/community/articles/what-is-that-domain-service-in-ddd-for-.net-developers-uqnpwjja)
+ * [Building an API Key Management System with ABP Framework](https://abp.io/community/articles/building-an-api-key-management-system-with-abp-framework-28gn4efw)
+* [Fahri Gedik](https://abp.io/community/members/fahrigedik)
+ * [Signal-Based Forms in Angular](https://abp.io/community/articles/signal-based-forms-in-angular-21-9qentsqs)
+
+Thanks to the ABP Community for all the content they have published. You can also [post your ABP related (text or video) content](https://abp.io/community/posts/create) to the ABP Community.
+
+## About the Next Version
+
+The next feature version will be 10.1. You can follow the [release planning here](https://github.com/abpframework/abp/milestones). Please [submit an issue](https://github.com/abpframework/abp/issues/new) if you have any problems with this version.
diff --git a/docs/en/Blog-Posts/2025-08-08 v10_0_Release_Stable/cover-image.png b/docs/en/Blog-Posts/2025-08-08 v10_0_Release_Stable/cover-image.png
new file mode 100644
index 0000000000..5453dcd4e8
Binary files /dev/null and b/docs/en/Blog-Posts/2025-08-08 v10_0_Release_Stable/cover-image.png differ
diff --git a/docs/en/Blog-Posts/2025-08-08 v10_0_Release_Stable/upgrade-abp-packages.png b/docs/en/Blog-Posts/2025-08-08 v10_0_Release_Stable/upgrade-abp-packages.png
new file mode 100644
index 0000000000..4ec1d19589
Binary files /dev/null and b/docs/en/Blog-Posts/2025-08-08 v10_0_Release_Stable/upgrade-abp-packages.png differ
diff --git a/docs/en/Blog-Posts/2025-10-23-ABP-is-Sponsoring-DotNET-Conf-2025/post.md b/docs/en/Blog-Posts/2025-10-23-ABP-is-Sponsoring-DotNET-Conf-2025/post.md
new file mode 100644
index 0000000000..6f546ee392
--- /dev/null
+++ b/docs/en/Blog-Posts/2025-10-23-ABP-is-Sponsoring-DotNET-Conf-2025/post.md
@@ -0,0 +1,20 @@
+### ABP is Sponsoring .NET Conf 2025\!
+
+We are very excited to announce that **ABP is a proud sponsor of .NET Conf 2025\!** This year marks the 15th online conference, celebrating the launch of .NET 10 and bringing together the global .NET community for three days\!
+
+Mark your calendar for **November 11th-13th** because you do not want to miss the biggest .NET virtual event of the year\!
+
+### About .NET Conf
+
+.NET Conference has always been **a free, virtual event, creating a world-class, engaging experience for developers** across the globe. This year, the conference is bigger than ever, drawing over 100 thousand live viewers and sponsoring hundreds of local community events worldwide\!
+
+### What to Expect
+
+**The .NET 10 Launch:** The event kicks off with the official release and deep-dive into the newest features of .NET 10\.
+
+**Three Days of Live Content:** Over the course of the event you'll get a wide selection of live sessions featuring speakers from the community and members of the .NET team.
+
+### Chance to Win a License\!
+
+As a proud sponsor, ABP is giving back to the community\! We are giving away one **ABP Personal License for a full year** to a lucky attendee of .NET Conf 2025\! To enter for a chance to win, simply register for the event [**here.**](https://www.dotnetconf.net/)
+
diff --git a/docs/en/Blog-Posts/2025-11-02-Repository-Pattern-in-the-Aspnetcore/post.md b/docs/en/Blog-Posts/2025-11-02-Repository-Pattern-in-the-Aspnetcore/post.md
new file mode 100644
index 0000000000..d1692471aa
--- /dev/null
+++ b/docs/en/Blog-Posts/2025-11-02-Repository-Pattern-in-the-Aspnetcore/post.md
@@ -0,0 +1,277 @@
+# Repository Pattern in the ASP.NET Core
+
+If you’ve built a .NET app with a database, you’ve likely used Entity Framework, Dapper, or ADO.NET. They’re useful tools; still, when they live inside your business logic or controllers, the code can become harder to keep tidy and to test.
+
+That’s where the **Repository Pattern** comes in.
+
+At its core, the Repository Pattern acts as a **middle layer between your domain and data access logic**. It abstracts the way you store and retrieve data, giving your application a clean separation of concerns:
+
+* **Separation of Concerns:** Business logic doesn’t depend on the database.
+* **Easier Testing:** You can replace the repository with a fake or mock during unit tests.
+* **Flexibility:** You can switch data sources (e.g., from SQL to MongoDB) without touching business logic.
+
+Let’s see how this works with a simple example.
+
+## A Simple Example with Product Repository
+
+Imagine we’re building a small e-commerce app. We’ll start by defining a repository interface for managing products.
+
+You can find the complete sample code in this GitHub repository:
+
+https://github.com/m-aliozkaya/RepositoryPattern
+
+### Domain model and context
+
+We start with a single entity and a matching `DbContext`.
+
+`Product.cs`
+
+```csharp
+using System.ComponentModel.DataAnnotations;
+
+namespace RepositoryPattern.Web.Models;
+
+public class Product
+{
+ public int Id { get; set; }
+
+ [Required, StringLength(64)]
+ public string Name { get; set; } = string.Empty;
+
+ [Range(0, double.MaxValue)]
+ public decimal Price { get; set; }
+
+ [StringLength(256)]
+ public string? Description { get; set; }
+
+ public int Stock { get; set; }
+}
+```
+
+`"AppDbContext.cs`
+
+```csharp
+using Microsoft.EntityFrameworkCore;
+using RepositoryPattern.Web.Models;
+
+namespace RepositoryPattern.Web.Data;
+
+public class AppDbContext(DbContextOptions options) : DbContext(options)
+{
+ public DbSet Products => Set();
+}
+```
+
+### Generic repository contract and base class
+
+All entities share the same CRUD needs, so we define a generic interface and an EF Core implementation.
+
+`Repositories/IRepository.cs`
+
+```csharp
+using System.Linq.Expressions;
+
+namespace RepositoryPattern.Web.Repositories;
+
+public interface IRepository where TEntity : class
+{
+ Task GetByIdAsync(int id, CancellationToken cancellationToken = default);
+ Task> GetAllAsync(CancellationToken cancellationToken = default);
+ Task> GetListAsync(Expression> predicate, CancellationToken cancellationToken = default);
+ Task AddAsync(TEntity entity, CancellationToken cancellationToken = default);
+ Task UpdateAsync(TEntity entity, CancellationToken cancellationToken = default);
+ Task DeleteAsync(int id, CancellationToken cancellationToken = default);
+}
+```
+
+`Repositories/EfRepository.cs`
+
+```csharp
+using Microsoft.EntityFrameworkCore;
+using RepositoryPattern.Web.Data;
+
+namespace RepositoryPattern.Web.Repositories;
+
+public class EfRepository(AppDbContext context) : IRepository
+ where TEntity : class
+{
+ protected readonly AppDbContext Context = context;
+
+ public virtual async Task GetByIdAsync(int id, CancellationToken cancellationToken = default)
+ => await Context.Set().FindAsync([id], cancellationToken);
+
+ public virtual async Task> GetAllAsync(CancellationToken cancellationToken = default)
+ => await Context.Set().AsNoTracking().ToListAsync(cancellationToken);
+
+ public virtual async Task> GetListAsync(
+ System.Linq.Expressions.Expression> predicate,
+ CancellationToken cancellationToken = default)
+ => await Context.Set()
+ .AsNoTracking()
+ .Where(predicate)
+ .ToListAsync(cancellationToken);
+
+ public virtual async Task AddAsync(TEntity entity, CancellationToken cancellationToken = default)
+ {
+ await Context.Set().AddAsync(entity, cancellationToken);
+ await Context.SaveChangesAsync(cancellationToken);
+ }
+
+ public virtual async Task UpdateAsync(TEntity entity, CancellationToken cancellationToken = default)
+ {
+ Context.Set().Update(entity);
+ await Context.SaveChangesAsync(cancellationToken);
+ }
+
+ public virtual async Task DeleteAsync(int id, CancellationToken cancellationToken = default)
+ {
+ var entity = await GetByIdAsync(id, cancellationToken);
+ if (entity is null)
+ {
+ return;
+ }
+
+ Context.Set().Remove(entity);
+ await Context.SaveChangesAsync(cancellationToken);
+ }
+}
+```
+
+Reads use `AsNoTracking()` to avoid tracking overhead, while write methods call `SaveChangesAsync` to keep the sample straightforward.
+
+### Product-specific repository
+
+Products need one extra query: list the items that are almost out of stock. We extend the generic repository with a dedicated interface and implementation.
+
+`Repositories/IProductRepository.cs`
+
+```csharp
+using RepositoryPattern.Web.Models;
+
+namespace RepositoryPattern.Web.Repositories;
+
+public interface IProductRepository : IRepository
+{
+ Task> GetLowStockProductsAsync(int threshold, CancellationToken cancellationToken = default);
+}
+```
+
+`Repositories/ProductRepository.cs`
+
+```csharp
+using Microsoft.EntityFrameworkCore;
+using RepositoryPattern.Web.Data;
+using RepositoryPattern.Web.Models;
+
+namespace RepositoryPattern.Web.Repositories;
+
+public class ProductRepository(AppDbContext context) : EfRepository(context), IProductRepository
+{
+ public Task> GetLowStockProductsAsync(int threshold, CancellationToken cancellationToken = default) =>
+ Context.Products
+ .AsNoTracking()
+ .Where(product => product.Stock <= threshold)
+ .OrderBy(product => product.Stock)
+ .ToListAsync(cancellationToken);
+}
+```
+
+### 🧩 A Note on Unit of Work
+
+The Repository Pattern is often used together with the **Unit of Work** pattern to manage transactions efficiently.
+
+> 💡 *If you want to dive deeper into the Unit of Work pattern, check out our separate blog post dedicated to that topic. https://abp.io/community/articles/lv4v2tyf
+
+### Service layer and controller
+
+Controllers depend on a service, and the service depends on the repository. That keeps HTTP logic and data logic separate.
+
+`Services/ProductService.cs`
+
+```csharp
+using RepositoryPattern.Web.Models;
+using RepositoryPattern.Web.Repositories;
+
+namespace RepositoryPattern.Web.Services;
+
+public class ProductService(IProductRepository productRepository)
+{
+ private readonly IProductRepository _productRepository = productRepository;
+
+ public Task> GetProductsAsync(CancellationToken cancellationToken = default) =>
+ _productRepository.GetAllAsync(cancellationToken);
+
+ public Task> GetLowStockAsync(int threshold, CancellationToken cancellationToken = default) =>
+ _productRepository.GetLowStockProductsAsync(threshold, cancellationToken);
+
+ public Task GetByIdAsync(int id, CancellationToken cancellationToken = default) =>
+ _productRepository.GetByIdAsync(id, cancellationToken);
+
+ public Task CreateAsync(Product product, CancellationToken cancellationToken = default) =>
+ _productRepository.AddAsync(product, cancellationToken);
+
+ public Task UpdateAsync(Product product, CancellationToken cancellationToken = default) =>
+ _productRepository.UpdateAsync(product, cancellationToken);
+
+ public Task DeleteAsync(int id, CancellationToken cancellationToken = default) =>
+ _productRepository.DeleteAsync(id, cancellationToken);
+}
+```
+
+`Controllers/ProductsController.cs`
+
+```csharp
+using Microsoft.AspNetCore.Mvc;
+using RepositoryPattern.Web.Models;
+using RepositoryPattern.Web.Services;
+
+namespace RepositoryPattern.Web.Controllers;
+
+public class ProductsController(ProductService productService) : Controller
+{
+ private readonly ProductService _productService = productService;
+
+ public async Task Index(CancellationToken cancellationToken)
+ {
+ const int lowStockThreshold = 5;
+ var products = await _productService.GetProductsAsync(cancellationToken);
+ var lowStock = await _productService.GetLowStockAsync(lowStockThreshold, cancellationToken);
+
+ return View(new ProductListViewModel(products, lowStock, lowStockThreshold));
+ }
+
+ // remaining CRUD actions call through ProductService in the same way
+}
+```
+
+The controller never reaches for `AppDbContext`. Every operation travels through the service, which keeps tests simple and makes future refactors easier.
+
+### Dependency registration and seeding
+
+The last step is wiring everything up in `Program.cs`.
+
+```csharp
+builder.Services.AddDbContext(options =>
+ options.UseInMemoryDatabase("ProductsDb"));
+builder.Services.AddScoped(typeof(IRepository<>), typeof(EfRepository<>));
+builder.Services.AddScoped();
+builder.Services.AddScoped();
+```
+
+The sample also seeds three products so the list page shows data on first run.
+
+Run the site with:
+
+```powershell
+dotnet run --project RepositoryPattern.Web
+```
+
+## How ABP approaches the same idea
+
+ABP includes generic repositories by default (`IRepository`), so you often skip writing the implementation layer shown above. You inject the interface into an application service, call methods like `InsertAsync` or `CountAsync`, and ABP’s Unit of Work handles the transaction. When you need custom queries, you can still derive from `EfCoreRepository` and add them.
+
+For more details, check out the official ABP documentation on repositories: https://abp.io/docs/latest/framework/architecture/domain-driven-design/repositories
+
+### Closing note
+
+This setup keeps data access tidy without being heavy. Start with the generic repository, add small extensions per entity, pass everything through services, and register the dependencies once. Whether you hand-code it or let ABP supply the repository, the structure stays the same and your controllers remain clean.
diff --git a/docs/en/Community-Articles/2025-10-17-5-Things-Deploy-Clustered-Environment/POST.md b/docs/en/Community-Articles/2025-10-17-5-Things-Deploy-Clustered-Environment/POST.md
new file mode 100644
index 0000000000..e6c0eb4601
--- /dev/null
+++ b/docs/en/Community-Articles/2025-10-17-5-Things-Deploy-Clustered-Environment/POST.md
@@ -0,0 +1,88 @@
+# 5 Things You Should Keep in Mind When Deploying to a Clustered Environment
+
+Let’s be honest — moving from a single server to a cluster sounds simple on paper.
+You just add a few more machines, right?
+In practice, it’s the moment when small architectural mistakes start to grow legs.
+Below are a few things that experienced engineers usually double-check before pressing that “Deploy” button.
+
+---
+
+## 1️⃣ Managing State the Right Way
+
+Each request in a cluster might hit a different machine.
+If your application keeps user sessions or cache in memory, that data probably won’t exist on the next node.
+That’s why many teams decide to push state out of the app itself.
+
+
+
+**A few real-world tips:**
+- Keep sessions in **Redis** or something similar instead of local memory.
+- Design endpoints so they don’t rely on earlier requests.
+- Don’t assume the same server will handle two requests in a row — it rarely does.
+
+---
+
+## 2️⃣ Shared Files and Where to Put Them
+
+Uploading files to local disk? That’s going to hurt in a cluster.
+Other nodes can’t reach those files, and you’ll spend hours wondering why images disappear.
+
+
+
+**Better habits:**
+- Push uploads to **S3**, **Azure Blob**, or **Google Cloud Storage**.
+- Send logs to a shared location instead of writing to local files.
+- Keep environment configs in a central place so each node starts with the same settings.
+
+---
+
+## 3️⃣ Database Connections Aren’t Free
+
+Every node opens its own database connections.
+Ten nodes with twenty connections each — that’s already two hundred open sessions.
+The database might not love that.
+
+
+
+**What helps:**
+- Put a cap on your connection pools.
+- Avoid keeping transactions open for too long.
+- Tune indexes and queries before scaling horizontally.
+
+---
+
+## 4️⃣ Logging and Observability Matter More Than You Think
+
+When something breaks in a distributed system, it’s never obvious which server was responsible.
+That’s why observability isn’t optional anymore.
+
+
+
+**Consider this:**
+- Stream logs to **ELK**, **Datadog**, or **Grafana Loki**.
+- Add a **trace ID** to every incoming request and propagate it across services.
+- Watch key metrics with **Prometheus** and visualize them in Grafana dashboards.
+
+---
+
+## 5️⃣ Background Jobs and Message Queues
+
+If more than one node runs the same job, you might process the same data twice — or delete something by mistake.
+You don’t want that kind of excitement in production.
+
+
+
+**A few precautions:**
+- Use a **distributed lock** or **leader election** system.
+- Make jobs **idempotent**, so running them twice doesn’t break data.
+- Centralize queue consumers or use a proper task scheduler.
+
+---
+
+## Wrapping Up
+
+Deploying to a cluster isn’t only about scaling up — it’s about staying stable when you do.
+Systems that handle state, logging, and background work correctly tend to age gracefully.
+Everything else eventually learns the hard way.
+
+> A cluster doesn’t fix design flaws — it magnifies them.
diff --git a/docs/en/Community-Articles/2025-10-17-5-Things-Deploy-Clustered-Environment/all.png b/docs/en/Community-Articles/2025-10-17-5-Things-Deploy-Clustered-Environment/all.png
new file mode 100644
index 0000000000..71cbe984c4
Binary files /dev/null and b/docs/en/Community-Articles/2025-10-17-5-Things-Deploy-Clustered-Environment/all.png differ
diff --git a/docs/en/Community-Articles/2025-10-17-5-Things-Deploy-Clustered-Environment/background.png b/docs/en/Community-Articles/2025-10-17-5-Things-Deploy-Clustered-Environment/background.png
new file mode 100644
index 0000000000..4d802e409d
Binary files /dev/null and b/docs/en/Community-Articles/2025-10-17-5-Things-Deploy-Clustered-Environment/background.png differ
diff --git a/docs/en/Community-Articles/2025-10-17-5-Things-Deploy-Clustered-Environment/cover-image.png b/docs/en/Community-Articles/2025-10-17-5-Things-Deploy-Clustered-Environment/cover-image.png
new file mode 100644
index 0000000000..be4c03fda0
Binary files /dev/null and b/docs/en/Community-Articles/2025-10-17-5-Things-Deploy-Clustered-Environment/cover-image.png differ
diff --git a/docs/en/Community-Articles/2025-10-17-5-Things-Deploy-Clustered-Environment/database.png b/docs/en/Community-Articles/2025-10-17-5-Things-Deploy-Clustered-Environment/database.png
new file mode 100644
index 0000000000..4a54b6f031
Binary files /dev/null and b/docs/en/Community-Articles/2025-10-17-5-Things-Deploy-Clustered-Environment/database.png differ
diff --git a/docs/en/Community-Articles/2025-10-17-5-Things-Deploy-Clustered-Environment/dev-to.md b/docs/en/Community-Articles/2025-10-17-5-Things-Deploy-Clustered-Environment/dev-to.md
new file mode 100644
index 0000000000..d6df7eea53
--- /dev/null
+++ b/docs/en/Community-Articles/2025-10-17-5-Things-Deploy-Clustered-Environment/dev-to.md
@@ -0,0 +1,27 @@
+# 5 Things You Should Keep in Mind When Deploying to a Clustered Environment
+
+Let’s be honest — moving from a single server to a cluster sounds simple on paper.
+You just add a few more machines, right?
+In practice, it’s the moment when small architectural mistakes start to grow legs.
+Below are a few things that experienced engineers usually double-check before pressing that “Deploy” button.
+
+---
+
+## 1️⃣ Managing State the Right Way
+---
+
+## 2️⃣ Shared Files and Where to Put Them
+---
+
+## 3️⃣ Database Connections Aren’t Free
+---
+
+## 4️⃣ Logging and Observability Matter More Than You Think
+---
+
+## 5️⃣ Background Jobs and Message Queues
+---
+
+
+
+👉 Read the full guide here: [5 Things You Should Keep in Mind When Deploying to a Clustered Environment](https://abp.io/community/articles/)
\ No newline at end of file
diff --git a/docs/en/Community-Articles/2025-10-17-5-Things-Deploy-Clustered-Environment/logging.png b/docs/en/Community-Articles/2025-10-17-5-Things-Deploy-Clustered-Environment/logging.png
new file mode 100644
index 0000000000..c3100a672a
Binary files /dev/null and b/docs/en/Community-Articles/2025-10-17-5-Things-Deploy-Clustered-Environment/logging.png differ
diff --git a/docs/en/Community-Articles/2025-10-17-5-Things-Deploy-Clustered-Environment/shared.png b/docs/en/Community-Articles/2025-10-17-5-Things-Deploy-Clustered-Environment/shared.png
new file mode 100644
index 0000000000..0331ce4a6a
Binary files /dev/null and b/docs/en/Community-Articles/2025-10-17-5-Things-Deploy-Clustered-Environment/shared.png differ
diff --git a/docs/en/Community-Articles/2025-10-17-5-Things-Deploy-Clustered-Environment/stateless.png b/docs/en/Community-Articles/2025-10-17-5-Things-Deploy-Clustered-Environment/stateless.png
new file mode 100644
index 0000000000..6b12c03db8
Binary files /dev/null and b/docs/en/Community-Articles/2025-10-17-5-Things-Deploy-Clustered-Environment/stateless.png differ
diff --git a/docs/en/Community-Articles/2025-10-17-Optimize-Your-App-For-Production/Post.md b/docs/en/Community-Articles/2025-10-17-Optimize-Your-App-For-Production/Post.md
index 74aaa56477..02790fde8b 100644
--- a/docs/en/Community-Articles/2025-10-17-Optimize-Your-App-For-Production/Post.md
+++ b/docs/en/Community-Articles/2025-10-17-Optimize-Your-App-For-Production/Post.md
@@ -247,5 +247,5 @@ In production run migrations manually, never do it on app startup. That way you
Use [Polly](https://www.pollydocs.org/) for retries, timeouts and circuit breakers for your DB or HTTP calls. Handles short outages gracefully
-To keep the article short and **for the better readability I spitted it into 2 parts 👉 [Continue with the second part here](Post2.md)...
+*To keep the article short and for the better readability I spitted it into 2 parts 👉 [Continue with the second part here](https://abp.io/community/articles/optimize-your-dotnet-app-for-production-for-any-.net-app-2-78xgncpi)...*
diff --git a/docs/en/Community-Articles/2025-10-17-Optimize-Your-App-For-Production/Post2.md b/docs/en/Community-Articles/2025-10-17-Optimize-Your-App-For-Production/Post2.md
index ad1f5e6433..8d5aca4a1a 100644
--- a/docs/en/Community-Articles/2025-10-17-Optimize-Your-App-For-Production/Post2.md
+++ b/docs/en/Community-Articles/2025-10-17-Optimize-Your-App-For-Production/Post2.md
@@ -258,3 +258,10 @@ Sometimes arguing with our lover is good. We can see her/his face before marryin
- GitHub address: https://github.com/codesenberg/bombardier
[](https://trends.google.com/trends/explore?cat=31&q=bombardier%20%2B%20benchmarking,k6%20%2B%20benchmarking)
+
+## Summary
+
+In summary, I listed 11 items for optimizing a .NET application for production; Covering build configuration, hosting setup, runtime behavior, data access, telemetry, containerization, security, startup performance and reliability under load. By applying the checklist from Part 1 and Part 2 of this series, leveraging techniques like trimmed releases, server GC, minimal payloads, pooled `DbContexts`, OpenTelemetry, multi-stage Docker builds, HTTPS enforcement, and proper shutdown handling—you’ll improve your app’s durability, scalability and maintainability under real-world traffic and production constraints. Each item is a checkpoint and you’ll be able to deliver a robust, high-performing .NET application ready for live users.
+
+🎉 Want top-tier .NET performance without the headaches? Try [ABP Framework](https://abp.io?utm_source=alper-ebicoglu-performance-article) for best-performance and skip all the hustles of .NET app development.
+
diff --git a/docs/en/Community-Articles/2025-10-17-Optimize-Your-App-For-Production/cover-2.png b/docs/en/Community-Articles/2025-10-17-Optimize-Your-App-For-Production/cover-2.png
new file mode 100644
index 0000000000..4f466fd11c
Binary files /dev/null and b/docs/en/Community-Articles/2025-10-17-Optimize-Your-App-For-Production/cover-2.png differ
diff --git a/docs/en/Community-Articles/2025-10-17-Optimize-Your-App-For-Production/cover.png b/docs/en/Community-Articles/2025-10-17-Optimize-Your-App-For-Production/cover.png
index f6387250b4..f9935df03c 100644
Binary files a/docs/en/Community-Articles/2025-10-17-Optimize-Your-App-For-Production/cover.png and b/docs/en/Community-Articles/2025-10-17-Optimize-Your-App-For-Production/cover.png differ
diff --git a/docs/en/Community-Articles/2025-10-20-The-ASP-DotNET-Core-Dependency-Injection System/post.md b/docs/en/Community-Articles/2025-10-20-The-ASP-DotNET-Core-Dependency-Injection System/post.md
index ccb1c38cbc..0a3959b44f 100644
--- a/docs/en/Community-Articles/2025-10-20-The-ASP-DotNET-Core-Dependency-Injection System/post.md
+++ b/docs/en/Community-Articles/2025-10-20-The-ASP-DotNET-Core-Dependency-Injection System/post.md
@@ -1135,6 +1135,8 @@ builder.Services.AddHostedService();
This pattern ensures that each run of the worker uses a new `DbContext`, preventing problems such as memory leaks or stale data.
+> While this example uses a simple `Task.Delay` loop within the `BackgroundService`, a robust pattern for managing decoupled background tasks involves an in memory queue. You can learn how to build this system by following this guide: [How to Build an In Memory Background Job Queue in ASP.NET Core From Scratch](https://abp.io/community/articles/how-to-build-an-in-memory-background-job-queue-in-asp.net-core-from-scratch-pai2zmtr).
+
## Conclusion
Understanding the **ASP.NET Core Dependency Injection** framework is essential for any .NET developer. By understanding the built in IoC container, choosing the right service lifecycles, and opting for explicit constructor injection, you can create modular, testable, and maintainable applications.
@@ -1169,4 +1171,4 @@ The transition from legacy, fragmented DI environments to a unified, performant,
- [IHttpClientFactory with .NET](https://learn.microsoft.com/en-us/dotnet/core/extensions/httpclient-factory)
- [Keyed Services DI Container](https://learn.microsoft.com/en-us/aspnet/core/fundamentals/dependency-injection?view=aspnetcore-9.0#keyed-services)
- [Use Scoped Services Within a Scoped Service](https://learn.microsoft.com/en-us/dotnet/core/extensions/scoped-service)
-- [Scrutor](https://github.com/khellang/Scrutor)
\ No newline at end of file
+- [Scrutor](https://github.com/khellang/Scrutor)
diff --git a/docs/en/Community-Articles/2025-10-31-Exceptions-vs-Return-Codes/Cover.png b/docs/en/Community-Articles/2025-10-31-Exceptions-vs-Return-Codes/Cover.png
new file mode 100644
index 0000000000..01f7ec061c
Binary files /dev/null and b/docs/en/Community-Articles/2025-10-31-Exceptions-vs-Return-Codes/Cover.png differ
diff --git a/docs/en/Community-Articles/2025-10-31-Exceptions-vs-Return-Codes/Post.md b/docs/en/Community-Articles/2025-10-31-Exceptions-vs-Return-Codes/Post.md
new file mode 100644
index 0000000000..3cfbd146b0
--- /dev/null
+++ b/docs/en/Community-Articles/2025-10-31-Exceptions-vs-Return-Codes/Post.md
@@ -0,0 +1,98 @@
+# **Return Code vs Exceptions: Which One is Better?**
+
+Alright, so this debate pops up every few months on dev subreddits and forums
+
+> *Should you use return codes or exceptions for error handling?*
+
+And honestly, there’s no %100 right answer here! Both have pros/cons, and depending on the language or context, one might make more sense than the other. Let’s see...
+
+------
+
+## 1. Return Codes --- Said to be "Old School Way" ---
+
+Return codes (like `0` for success, `-1` for failure, etc.) are the OG method. You mostly see them everywhere in C and C++.
+They’re super explicit, the function literally *returns* the result of the operation.
+
+### ➕ Advantages of returning codes:
+
+- You *always* know when something went wrong
+- No hidden control flow — what you see is what you get
+- Usually faster (no stack unwinding, no exception overhead)
+- Easy to use in systems programming, embedded stuff, or performance-critical code
+
+### ➖ Disadvantages of returning codes:
+
+- It’s easy to forget to check the return value (and boom, silent failure 😬)
+- Makes code noisy... Everry function call followed by `if (result != SUCCESS)` gets annoying
+- No stack trace or context unless you manually build one
+
+**For example:**
+
+```csharp
+try
+{
+ await SendEmailAsync();
+}
+catch (Exception e)
+{
+ Log.Exception(e.ToString());
+ return -1;
+}
+```
+
+Looks fine… until you forget one of those `if` conditions somewhere.
+
+------
+
+## 2. Exceptions --- The Fancy & Modern Way ---
+
+Exceptions came in later, mostly with higher-level languages like Java, C#, and Python.
+The idea is that you *throw* an error and handle it *somewhere else*.
+
+### ➕ Advantages of throwing exceptions:
+
+- Cleaner code... You can focus on the happy path and handle errors separately
+- Can carry detailed info (stack traces, messages, inner exceptions...)
+- Easier to handle complex error propagation
+
+### ➖ Disadvantages of throwing exceptions:
+
+- Hidden control flow — you don’t always see what might throw
+- Performance hit (esp. in tight loops or low-level systems)
+- Overused in some codebases (“everything throws everything”)
+
+**Example:**
+
+```csharp
+try
+{
+ await SendEmailAsync();
+}
+catch (Exception e)
+{
+ Log.Exception(e.ToString());
+ throw e;
+}
+```
+
+Way cleaner, but if `SendEmailAsync()` is deep in your call stack and it fails, it can be tricky to know exactly what went wrong unless you log properly.
+
+------
+
+### And Which One’s Better? ⚖️
+
+Depends on what you’re building.
+
+- **Low-level systems, drivers, real-time stuff 👉 Return codes.** Performance and control matter more.
+- **Application-level, business logic, or high-level APIs 👉 Exceptions.** Cleaner and easier to maintain.
+
+And honestly, mixing both sometimes makes sense.
+For example, you can use return codes internally and exceptions at the boundary of your API to surface meaningful errors to the user.
+
+------
+
+### Conclusion
+
+Return codes = simple, explicit, but messy.t
+Exceptions = clean, powerful, but can bite you.
+Use what fits your project and your team’s sanity level 😅.
\ No newline at end of file
diff --git a/docs/en/Community-Articles/2025-11-05-UI-UX-Trends-That-Will-Shape-2026/bento.png b/docs/en/Community-Articles/2025-11-05-UI-UX-Trends-That-Will-Shape-2026/bento.png
new file mode 100644
index 0000000000..bb16a71259
Binary files /dev/null and b/docs/en/Community-Articles/2025-11-05-UI-UX-Trends-That-Will-Shape-2026/bento.png differ
diff --git a/docs/en/Community-Articles/2025-11-05-UI-UX-Trends-That-Will-Shape-2026/dark-mode.png b/docs/en/Community-Articles/2025-11-05-UI-UX-Trends-That-Will-Shape-2026/dark-mode.png
new file mode 100644
index 0000000000..612a786a71
Binary files /dev/null and b/docs/en/Community-Articles/2025-11-05-UI-UX-Trends-That-Will-Shape-2026/dark-mode.png differ
diff --git a/docs/en/Community-Articles/2025-11-05-UI-UX-Trends-That-Will-Shape-2026/large.png b/docs/en/Community-Articles/2025-11-05-UI-UX-Trends-That-Will-Shape-2026/large.png
new file mode 100644
index 0000000000..544214db08
Binary files /dev/null and b/docs/en/Community-Articles/2025-11-05-UI-UX-Trends-That-Will-Shape-2026/large.png differ
diff --git a/docs/en/Community-Articles/2025-11-05-UI-UX-Trends-That-Will-Shape-2026/post.md b/docs/en/Community-Articles/2025-11-05-UI-UX-Trends-That-Will-Shape-2026/post.md
new file mode 100644
index 0000000000..e0f9ec3b5f
--- /dev/null
+++ b/docs/en/Community-Articles/2025-11-05-UI-UX-Trends-That-Will-Shape-2026/post.md
@@ -0,0 +1,112 @@
+# UI & UX Trends That Will Shape 2026
+
+Cinematic, gamified, high-wow-factor websites with scroll-to-play videos or scroll-to-tell stories are wonderful to experience, but you won't find these trends in this article. If you're interested in design trends directly related to the software world, such as **performance**, **accessibility**, **understandability**, and **efficiency**, grab a cup of coffee and enjoy.
+
+As we approach the end of 2025, I'd like to share with you the most important user interface and user experience design trends that have become more of a **toolkit** than a trend, and that continue to evolve and become a part of our lives. I predict we'll see a lot of them in 2026\.
+
+## 1\. Simplicity and Speed
+
+Designing understandable and readable applications is becoming far more important than designing in line with trends and fashion. In the software and business world, preferences are shifting more and more toward the **right design** over the cool design. As designers developing a product whose direct target audience is software developers, we design our products for the designers' enjoyment, but for the **end user's ease of use**.
+
+Users no longer care so much about the flashiness of a website. True converts are primarily interested in your product, service, or content. What truly matters to them is how easily and quickly they can access the information they're looking for.
+
+More users, more sales, better promotion, and a higher conversion rate... The elements that serve these goals are optimized solutions and thoughtful details in our designs, more than visual displays.
+
+If the "loading" icon appears too often on your digital product, you might not be doing it right. If you fail to optimize speed, the temporary effect of visual displays won't be enough to convert potential users into customers. Remember, the moment people start waiting, you've lost at least half of them.
+
+## 2\. Dark Mode \- Still, and Forever
+
+
+Dark Mode is no longer an option; it's a **standard**. It's become a necessity, not a choice, especially for users who spend hours staring at screens and are accustomed to dark themes in code editors and terminals. However, the approach to dark mode isn't simply about inverting colors; it's much deeper than that. The key is managing contrast and depth.
+
+The layer hierarchy established in a light-colored design doesn't lose its impact when switched to dark mode. The colors, shadows, highlights, and contrasting elements used to create an **easily perceivable hierarchy** should be carefully considered for each mode. Our [LeptonX theme](https://leptontheme.com/)'s Light, Dark, Semi-dark, and System modes offer valuable insights you might want to explore.
+
+You might also want to take a look at the dark and light modes we designed with these elements in mind in [ABP Studio](https://abp.io/get-started) and the [ABP.io Documents page](https://abp.io/docs/latest/).
+
+## 3\. Bento Grid \- A Timeless Trend
+
+
+People don't read your website; they **scan** it.
+
+Bento Grid, an indispensable trend for designers looking to manage their attention, looks set to remain a staple in 2026, just as it was in 2025\. No designer should ignore the fact that many tech giants, especially Apple and Samsung, are still using bento grids on their websites. The bento grid appears not only on websites but also in operating systems, VR headset interfaces, game console interfaces, and game designs.
+
+The golden rule is **contrast** and **balance**.
+
+The attractiveness and effectiveness of bento designs depend on certain factors you should consider when implementing them. If you ignore these rules, even with a proven method like bento, you can still alienate users.
+
+The bento grid is one of the best ways to display different types of content inclusively. When used correctly, it's also a great way to manipulate reading order, guiding the user's eye. Improper contrast and hierarchy can also create a negative experience. Designers should use this to guide the reader's eye: "Read here first, then read here."
+
+When creating a bento, you inherently have to sacrifice some of your "whitespace." This design has many elements for the user to focus on, and it actually strays from our first point, "Simplicity". Bento design, whose boundaries are drawn from the outset and independent of content, requires care not to include more or less than what is necessary. Too much content makes it boring; too little content makes it very close to meaningless.
+
+Bento grids should aim for a balanced design by using both simple text and sophisticated visuals. This visual can be an illustration, a video that starts playing when hovered over, a static image, or a large title. Only one or two cards on the screen at a time should have attention.
+
+## 4\. Larger Fonts, High Readability
+
+
+Large fonts have been a trend for several years, and it seems web designers are becoming more and more bold. The increasing preference for larger fonts every year is a sign that this trend will continue into 2026\. This trend is about more than just using large font sizes in headlines.
+
+Creating a cohesive typographic scale and proper line height and letter spacing are critical elements to consider when creating this trend. As the font size increases, line height should decrease, and the space between letters should be narrower.
+
+The browser default font size, which we used to see in body text and paragraphs and has now become standard, is 16 pixels. In the last few years, we've started seeing body font sizes of 17 or 18 pixels more frequently. The increasing importance of readability every year makes this more common. Font sizes in rem values, rather than px, provide the most efficient results.
+
+## 5\. Micro Animations
+
+Unless you're a web design agency designing a website to impress potential clients, you should avoid excessive changes, including excessive image changes during scrolling, and scroll direction changes. There's still room for oversized images and scroll animations. But be sure to create the visuals yourself.
+
+The trend I'm talking about here is **micro animations**, not macro ones. Small movements, not large ones.
+
+The animation approach of 2025 is **functional** and **performance-sensitive**.
+
+Microanimations exist to provide immediate feedback to the user. Instant feedback, like a button's shadow increasing when hovered over, a button's slight collapse when clicked, or a "Save" icon changing to a "Confirm" icon when saving data, keeps your designs alive.
+
+We see the real impact of the micro-animation trend in static, non-action visuals. The use of non-button elements in your designs, accentuated by micro-movements such as scrolling or hovering, seems poised to continue to create macro effects in 2026\.
+
+## 6\. Real Images and Human-like Touches
+
+People quickly spot a fake. It's very difficult to convince a user who visits your website for the first time and doesn't trust you. **First impressions** matter.
+
+Real photographs, actual product screenshots, and brand-specific illustrations will continue to be among the elements we want to see in **trust-focused** designs in 2026\.
+
+In addition to flawless work done by AI, vivid, real-life visuals, accompanied by deliberate imperfections, hand-drawn details, or designed products that convey the message, "A human made this site\!", will continue to feel warmer and more welcoming.
+
+The human touch is evident not only in the visuals but also in your **content and text**.
+
+In 2026, you'll need more **human-like touches** that will make your design stand out among the thousands of similar websites rapidly generated by AI.
+
+## 7\. Accessibility \- No Longer an Option, But a Legal and Ethical Obligation
+
+Accessibility, once considered a nice-to-do thing in recent years, is now becoming a **necessity** in 2026 and beyond. Global regulations like the European Accessibility Act require all digital products to comply with WCAG standards.
+
+All design and software improvements you make to ensure end users can fully perform their tasks in your products, regardless of their temporary or permanent disabilities, should be viewed as ethical and commercial requirements, not as a requirement to comply with these standards.
+
+The foundation of accessibility in design is to use semantic HTML for screen readers, provide full keyboard control of all interactive elements, and clearly communicate the roles of complex components to the development team.
+
+## 8\. Intentional Friction
+
+Steve Krug, the father of UX design, started the trend of designing everything at a hyper-usable level with his book "Don't Make Me Think." As web designers, we've embraced this idea so much that all we care about is getting the user to their destination in the shortest possible scenario and as quickly as possible. This has required so many understandability measures that, after a while, it's starting to feel like fooling the user.
+
+In recent years, designers have started looking for ways to make things a little more challenging, rather than just getting the user to the result.
+
+When the end user visits your website, tries to understand exactly what it is at first glance, struggles a bit, and, after a little effort, becomes familiar with how your world works, they'll be more inclined to consider themselves a part of it.
+
+This has nothing to do with anti-usability. This philosophy is called Intentional Friction.
+
+This isn't a flaw; it's the pinnacle of error prevention. It's a step to prevent errors from occurring on autopilot and respects the user's ability to understand complex systems. Examples include reviewing the order summary or manually typing the project name when deleting a project on GitHub.
+
+## Bonus: Where Does Artificial Intelligence Fit In?
+
+Artificial intelligence will be an infrastructure in 2026, not a trend.
+
+As designers, we should leverage AI not to paint us a picture, but to make workflows more intelligent. In my opinion, this is the best use case for AI.
+
+AI can learn user behavior and adapt the interface accordingly. Real-time A/B testing can save us time by conducting a real-time content review. The ability to actively use AI in any area that allows you to accelerate your progress will take you a step further in your career.
+
+Since your users are always human, **don't be too eager** to incorporate AI-generated visuals into your design. Unless you're creating and selling a ready-made theme, you should **avoid** AI-generated visuals, random bento grids, and randomly generated content.
+
+You should definitely incorporate AI into your work for new content, new ideas, personal and professional development, and insights that will take your design a step further. But just as you don't design your website for designers to like, the same applies to AI. Humans, not robots, will experience your website. **AI-assisted**, not AI-generated, designs with a human touch are the trend I most expect seeing in 2026\.
+
+## Conclusion
+
+In the end, it's all fundamentally about respect for the user and their time. In 2026, our success as designers and developers will be measured not by how "cool" we are, but by how "efficient" and "reliable" a world we build for our users.
+
+Thank you for your time.
diff --git a/docs/en/Community-Articles/2025-11-08-what-is-that-domain-service-in-ddd-for-net-developers/cover-image.png b/docs/en/Community-Articles/2025-11-08-what-is-that-domain-service-in-ddd-for-net-developers/cover-image.png
new file mode 100644
index 0000000000..5ee2f50934
Binary files /dev/null and b/docs/en/Community-Articles/2025-11-08-what-is-that-domain-service-in-ddd-for-net-developers/cover-image.png differ
diff --git a/docs/en/Community-Articles/2025-11-08-what-is-that-domain-service-in-ddd-for-net-developers/images/abp-structure.png b/docs/en/Community-Articles/2025-11-08-what-is-that-domain-service-in-ddd-for-net-developers/images/abp-structure.png
new file mode 100644
index 0000000000..5c5639839c
Binary files /dev/null and b/docs/en/Community-Articles/2025-11-08-what-is-that-domain-service-in-ddd-for-net-developers/images/abp-structure.png differ
diff --git a/docs/en/Community-Articles/2025-11-08-what-is-that-domain-service-in-ddd-for-net-developers/images/ddd-layers.png b/docs/en/Community-Articles/2025-11-08-what-is-that-domain-service-in-ddd-for-net-developers/images/ddd-layers.png
new file mode 100644
index 0000000000..7307f1cbab
Binary files /dev/null and b/docs/en/Community-Articles/2025-11-08-what-is-that-domain-service-in-ddd-for-net-developers/images/ddd-layers.png differ
diff --git a/docs/en/Community-Articles/2025-11-08-what-is-that-domain-service-in-ddd-for-net-developers/images/money-transfer.png b/docs/en/Community-Articles/2025-11-08-what-is-that-domain-service-in-ddd-for-net-developers/images/money-transfer.png
new file mode 100644
index 0000000000..2ebf3b4fef
Binary files /dev/null and b/docs/en/Community-Articles/2025-11-08-what-is-that-domain-service-in-ddd-for-net-developers/images/money-transfer.png differ
diff --git a/docs/en/Community-Articles/2025-11-08-what-is-that-domain-service-in-ddd-for-net-developers/images/service-comparison.png b/docs/en/Community-Articles/2025-11-08-what-is-that-domain-service-in-ddd-for-net-developers/images/service-comparison.png
new file mode 100644
index 0000000000..498a438502
Binary files /dev/null and b/docs/en/Community-Articles/2025-11-08-what-is-that-domain-service-in-ddd-for-net-developers/images/service-comparison.png differ
diff --git a/docs/en/Community-Articles/2025-11-08-what-is-that-domain-service-in-ddd-for-net-developers/post.md b/docs/en/Community-Articles/2025-11-08-what-is-that-domain-service-in-ddd-for-net-developers/post.md
new file mode 100644
index 0000000000..7eca19a652
--- /dev/null
+++ b/docs/en/Community-Articles/2025-11-08-what-is-that-domain-service-in-ddd-for-net-developers/post.md
@@ -0,0 +1,592 @@
+# What is That Domain Service in DDD for .NET Developers?
+
+When you start applying **Domain-Driven Design (DDD)** in your .NET projects, you'll quickly meet some core building blocks: **Entities**, **Value Objects**, **Aggregates**, and finally… **Domain Services**.
+
+But what exactly *is* a Domain Service, and when should you use one?
+
+Let's break it down with practical examples and ABP Framework implementation patterns.
+
+---
+
+
+
+## The Core Idea of Domain Services
+
+A **Domain Service** represents **a domain concept that doesn't naturally belong to a single Entity or Value Object**, but still belongs to the **domain layer** - *not* to the application or infrastructure.
+
+In short:
+
+> If your business logic doesn't fit into a single Entity, but still expresses a business rule, that's a good candidate for a Domain Service.
+
+
+
+---
+
+## Example: Money Transfer Between Accounts
+
+Imagine a simple **banking system** where you can transfer money between accounts.
+
+```csharp
+public class Account : AggregateRoot
+{
+ public decimal Balance { get; private set; }
+
+ // Domain model should be created in a valid state.
+ public Account(decimal openingBalance = 0m)
+ {
+ if (openingBalance < 0)
+ throw new BusinessException("Opening balance cannot be negative.");
+ Balance = openingBalance;
+ }
+
+ public void Withdraw(decimal amount)
+ {
+ if (amount <= 0)
+ throw new BusinessException("Withdrawal amount must be positive.");
+ if (Balance < amount)
+ throw new BusinessException("Insufficient balance.");
+ Balance -= amount;
+ }
+
+ public void Deposit(decimal amount)
+ {
+ if (amount <= 0)
+ throw new BusinessException("Deposit amount must be positive.");
+ Balance += amount;
+ }
+}
+```
+
+> In a richer domain you might introduce a `Money` value object (amount + currency + rounding rules) instead of a raw `decimal` for stronger invariants.
+
+---
+
+## Implementing a Domain Service
+
+
+
+```csharp
+public class MoneyTransferManager : DomainService
+{
+ public void Transfer(Account from, Account to, decimal amount)
+ {
+ if (from is null) throw new ArgumentNullException(nameof(from));
+ if (to is null) throw new ArgumentNullException(nameof(to));
+ if (ReferenceEquals(from, to))
+ throw new BusinessException("Cannot transfer to the same account.");
+ if (amount <= 0)
+ throw new BusinessException("Transfer amount must be positive.");
+
+ from.Withdraw(amount);
+ to.Deposit(amount);
+ }
+}
+```
+
+> **Naming Convention**: ABP suggests using the `Manager` or `Service` suffix for domain services. We typically use `Manager` suffix (e.g., `IssueManager`, `OrderManager`).
+
+> **Note**: This is a synchronous domain operation. The domain service focuses purely on business rules without infrastructure concerns like database access or event publishing. For cross-cutting concerns, use Application Service layer or domain events.
+
+---
+
+## Domain Service vs. Application Service
+
+Here's a quick comparison:
+
+
+
+| Layer | Responsibility | Example |
+| ----------------------- | -------------------------------------------------------------------------------- | ---------------------------- |
+| **Domain Service** | Pure business rule spanning entities/aggregates | `MoneyTransferManager` |
+| **Application Service** | Orchestrates use cases, handles repositories, transactions, external systems | `BankAppService` |
+
+---
+
+## The Application Service Layer
+
+An **Application Service** orchestrates the domain logic and handles infrastructure concerns:
+
+
+
+```csharp
+public class BankAppService : ApplicationService
+{
+ private readonly IRepository _accountRepository;
+ private readonly MoneyTransferManager _moneyTransferManager;
+
+ public BankAppService(
+ IRepository accountRepository,
+ MoneyTransferManager moneyTransferManager)
+ {
+ _accountRepository = accountRepository;
+ _moneyTransferManager = moneyTransferManager;
+ }
+
+ public async Task TransferAsync(Guid fromId, Guid toId, decimal amount)
+ {
+ var from = await _accountRepository.GetAsync(fromId);
+ var to = await _accountRepository.GetAsync(toId);
+
+ _moneyTransferManager.Transfer(from, to, amount);
+
+ await _accountRepository.UpdateAsync(from);
+ await _accountRepository.UpdateAsync(to);
+ }
+}
+```
+
+> **Note**: Domain services are automatically registered to Dependency Injection with a **Transient** lifetime when inheriting from `DomainService`.
+
+---
+
+## Benefits of ABP's DomainService Base Class
+
+The `DomainService` base class gives you access to:
+
+- **Localization** (`IStringLocalizer L`) - Multi-language support for error messages
+- **Logging** (`ILogger Logger`) - Built-in logger for tracking operations
+- **Local Event Bus** (`ILocalEventBus LocalEventBus`) - Publish local domain events
+- **Distributed Event Bus** (`IDistributedEventBus DistributedEventBus`) - Publish distributed events
+- **GUID Generator** (`IGuidGenerator GuidGenerator`) - Sequential GUID generation for better database performance
+- **Clock** (`IClock Clock`) - Abstraction for date/time operations
+
+### Example with ABP Features
+
+> **Important**: While domain services *can* publish domain events using the event bus, they should remain focused on business rules. Consider whether event publishing belongs in the domain service or the application service based on your consistency boundaries.
+
+```csharp
+public class MoneyTransferredEvent
+{
+ public Guid FromAccountId { get; set; }
+ public Guid ToAccountId { get; set; }
+ public decimal Amount { get; set; }
+}
+
+public class MoneyTransferManager : DomainService
+{
+ public async Task TransferAsync(Account from, Account to, decimal amount)
+ {
+ if (from is null) throw new ArgumentNullException(nameof(from));
+ if (to is null) throw new ArgumentNullException(nameof(to));
+ if (ReferenceEquals(from, to))
+ throw new BusinessException(L["SameAccountTransferNotAllowed"]);
+ if (amount <= 0)
+ throw new BusinessException(L["InvalidTransferAmount"]);
+
+ // Log the operation
+ Logger.LogInformation(
+ "Transferring {Amount} from {From} to {To}", amount, from.Id, to.Id);
+
+ from.Withdraw(amount);
+ to.Deposit(amount);
+
+ // Publish local event for further policies (limits, notifications, audit, etc.)
+ await LocalEventBus.PublishAsync(
+ new MoneyTransferredEvent
+ {
+ FromAccountId = from.Id,
+ ToAccountId = to.Id,
+ Amount = amount
+ }
+ );
+ }
+}
+```
+
+> **Local Events**: By default, event handlers are executed within the same Unit of Work. If an event handler throws an exception, the database transaction is rolled back, ensuring consistency.
+
+---
+
+## Best Practices
+
+### 1. Keep Domain Services Pure and Focused on Business Rules
+
+Domain services should only contain business logic. They should not be responsible for application-level concerns like database transactions, authorization, or fetching entities from a repository.
+
+```csharp
+// Good ✅ Pure rule: receives aggregates already loaded.
+public class MoneyTransferManager : DomainService
+{
+ public void Transfer(Account from, Account to, decimal amount)
+ {
+ // Business rules and coordination
+ from.Withdraw(amount);
+ to.Deposit(amount);
+ }
+}
+
+// Bad ❌ Mixing application and domain concerns.
+// This logic belongs in an Application Service.
+public class MoneyTransferManager : DomainService
+{
+ private readonly IRepository _accountRepository;
+
+ public MoneyTransferManager(IRepository accountRepository)
+ {
+ _accountRepository = accountRepository;
+ }
+
+ public async Task TransferAsync(Guid fromId, Guid toId, decimal amount)
+ {
+ // Don't fetch entities inside a domain service.
+ var from = await _accountRepository.GetAsync(fromId);
+ var to = await _accountRepository.GetAsync(toId);
+
+ from.Withdraw(amount);
+ to.Deposit(amount);
+ }
+}
+```
+
+### 2. Leverage Entity Methods First
+
+Always prefer encapsulating business logic within an entity's methods when the logic belongs to a single aggregate. A domain service should only be used when a business rule spans multiple aggregates.
+
+```csharp
+// Good ✅ - Internal state change belongs in the entity
+public class Account : AggregateRoot
+{
+ public decimal Balance { get; private set; }
+
+ public void Withdraw(decimal amount)
+ {
+ if (Balance < amount)
+ throw new BusinessException("Insufficient balance");
+ Balance -= amount;
+ }
+}
+
+// Use Domain Service only when logic spans multiple aggregates
+public class MoneyTransferManager : DomainService
+{
+ public void Transfer(Account from, Account to, decimal amount)
+ {
+ from.Withdraw(amount); // Delegates to entity
+ to.Deposit(amount); // Delegates to entity
+ }
+}
+```
+
+### 3. Prefer Domain Services over Anemic Entities
+
+Avoid placing business logic that coordinates multiple entities directly into an application service. This leads to an "Anemic Domain Model," where entities are just data bags and the business logic is scattered in application services.
+
+```csharp
+// Bad ❌ - Business logic is in the Application Service (Anemic Domain)
+public class BankAppService : ApplicationService
+{
+ public async Task TransferAsync(Guid fromId, Guid toId, decimal amount)
+ {
+ var from = await _accountRepository.GetAsync(fromId);
+ var to = await _accountRepository.GetAsync(toId);
+
+ // This is domain logic and should be in a Domain Service
+ if (ReferenceEquals(from, to))
+ throw new BusinessException("Cannot transfer to the same account.");
+ if (amount <= 0)
+ throw new BusinessException("Transfer amount must be positive.");
+
+ from.Withdraw(amount);
+ to.Deposit(amount);
+ }
+}
+```
+
+### 4. Use Meaningful Names
+
+ABP recommends naming domain services with a `Manager` or `Service` suffix based on the business concept they represent.
+
+```csharp
+// Good ✅
+MoneyTransferManager
+OrderManager
+IssueManager
+InventoryAllocationService
+
+// Bad ❌
+AccountHelper
+OrderProcessor
+```
+
+---
+
+## Advanced Example: Order Processing with Inventory Check
+
+Here's a more complex scenario showing domain service interaction with domain abstractions:
+
+```csharp
+// Domain abstraction - defines contract but implementation is in infrastructure
+public interface IInventoryChecker : IDomainService
+{
+ Task IsAvailableAsync(Guid productId, int quantity);
+}
+
+public class OrderManager : DomainService
+{
+ private readonly IInventoryChecker _inventoryChecker;
+
+ public OrderManager(IInventoryChecker inventoryChecker)
+ {
+ _inventoryChecker = inventoryChecker;
+ }
+
+ // Validates and coordinates order processing with inventory
+ public async Task ProcessAsync(Order order, Inventory inventory)
+ {
+ // First pass: validate availability using domain abstraction
+ foreach (var item in order.Items)
+ {
+ if (!await _inventoryChecker.IsAvailableAsync(item.ProductId, item.Quantity))
+ {
+ throw new BusinessException(
+ L["InsufficientInventory", item.ProductId]);
+ }
+ }
+
+ // Second pass: perform reservations
+ foreach (var item in order.Items)
+ {
+ inventory.Reserve(item.ProductId, item.Quantity);
+ }
+
+ order.SetStatus(OrderStatus.Processing);
+ }
+}
+```
+
+> **Domain Abstractions**: The `IInventoryChecker` interface is a domain service contract. Its implementation can be in the infrastructure layer, but the contract belongs to the domain. This keeps the domain layer independent of infrastructure details while still allowing complex validations.
+
+> **Caution**: Always perform validation and action atomically within a single transaction to avoid race conditions (TOCTOU - Time Of Check Time Of Use).
+
+> **Transaction Boundaries**: When a domain service coordinates multiple aggregates, ensure the Application Service wraps the operation in a Unit of Work to maintain consistency. ABP's `[UnitOfWork]` attribute or Application Services' built-in UoW handling ensures this automatically.
+
+---
+
+## Common Pitfalls and How to Avoid Them
+
+### 1. Bloated Domain Services
+Don't let domain services become "god objects" that do everything. Keep them focused on a single business concept.
+
+```csharp
+// Bad ❌ - Too many responsibilities
+public class AccountManager : DomainService
+{
+ public void Transfer(Account from, Account to, decimal amount) { }
+ public void CalculateInterest(Account account) { }
+ public void GenerateStatement(Account account) { }
+ public void ValidateAddress(Account account) { }
+ public void SendNotification(Account account) { }
+}
+
+// Good ✅ - Split by business concept
+public class MoneyTransferManager : DomainService
+{
+ public void Transfer(Account from, Account to, decimal amount) { }
+}
+
+public class InterestCalculationManager : DomainService
+{
+ public void Calculate(Account account) { }
+}
+```
+
+### 2. Circular Dependencies Between Aggregates
+When domain services coordinate multiple aggregates, be careful about creating circular dependencies.
+
+```csharp
+// Consider using Domain Events instead of direct coupling
+public class OrderManager : DomainService
+{
+ public async Task ProcessAsync(Order order)
+ {
+ order.SetStatus(OrderStatus.Processing);
+
+ // Instead of directly modifying Customer aggregate here,
+ // publish an event that CustomerManager can handle
+ await LocalEventBus.PublishAsync(new OrderProcessedEvent
+ {
+ OrderId = order.Id,
+ CustomerId = order.CustomerId
+ });
+ }
+}
+```
+
+### 3. Confusing Domain Service with Domain Event Handlers
+Domain services orchestrate business operations. Domain event handlers react to state changes. Don't mix them.
+
+```csharp
+// Domain Service - Orchestrates business logic
+public class MoneyTransferManager : DomainService
+{
+ public async Task TransferAsync(Account from, Account to, decimal amount)
+ {
+ from.Withdraw(amount);
+ to.Deposit(amount);
+ await LocalEventBus.PublishAsync(
+ new MoneyTransferredEvent
+ {
+ FromAccountId = from.Id,
+ ToAccountId = to.Id,
+ Amount = amount
+ }
+ );
+ }
+}
+
+// Domain Event Handler - Reacts to domain events
+public class MoneyTransferredEventHandler :
+ ILocalEventHandler,
+ ITransientDependency
+{
+ public async Task HandleEventAsync(MoneyTransferredEvent eventData)
+ {
+ // Send notification, update analytics, etc.
+ }
+}
+```
+
+---
+
+## Testing Domain Services
+
+Domain services are easy to test because they have minimal dependencies:
+
+```csharp
+public class MoneyTransferManager_Tests
+{
+ [Fact]
+ public void Should_Transfer_Money_Between_Accounts()
+ {
+ // Arrange
+ var fromAccount = new Account(1000m);
+ var toAccount = new Account(500m);
+ var manager = new MoneyTransferManager();
+
+ // Act
+ manager.Transfer(fromAccount, toAccount, 200m);
+
+ // Assert
+ fromAccount.Balance.ShouldBe(800m);
+ toAccount.Balance.ShouldBe(700m);
+ }
+
+ [Fact]
+ public void Should_Throw_When_Insufficient_Balance()
+ {
+ var fromAccount = new Account(100m);
+ var toAccount = new Account(500m);
+ var manager = new MoneyTransferManager();
+
+ Should.Throw(() =>
+ manager.Transfer(fromAccount, toAccount, 200m));
+ }
+
+ [Fact]
+ public void Should_Throw_When_Amount_Is_NonPositive()
+ {
+ var fromAccount = new Account(100m);
+ var toAccount = new Account(100m);
+ var manager = new MoneyTransferManager();
+
+ Should.Throw(() =>
+ manager.Transfer(fromAccount, toAccount, 0m));
+ Should.Throw(() =>
+ manager.Transfer(fromAccount, toAccount, -5m));
+ }
+
+ [Fact]
+ public void Should_Throw_When_Same_Account()
+ {
+ var account = new Account(100m);
+ var manager = new MoneyTransferManager();
+
+ Should.Throw(() =>
+ manager.Transfer(account, account, 10m));
+ }
+}
+```
+
+### Integration Testing with ABP Test Infrastructure
+
+```csharp
+public class MoneyTransferManager_IntegrationTests : BankingDomainTestBase
+{
+ private readonly MoneyTransferManager _transferManager;
+ private readonly IRepository _accountRepository;
+
+ public MoneyTransferManager_IntegrationTests()
+ {
+ _transferManager = GetRequiredService();
+ _accountRepository = GetRequiredService>();
+ }
+
+ [Fact]
+ public async Task Should_Transfer_And_Persist_Changes()
+ {
+ // Arrange
+ var fromAccount = new Account(1000m);
+ var toAccount = new Account(500m);
+
+ await _accountRepository.InsertAsync(fromAccount);
+ await _accountRepository.InsertAsync(toAccount);
+ await UnitOfWorkManager.Current.SaveChangesAsync();
+
+ // Act
+ await _transferManager.TransferAsync(fromAccount, toAccount, 200m);
+ await UnitOfWorkManager.Current.SaveChangesAsync();
+
+ // Assert
+ var updatedFrom = await _accountRepository.GetAsync(fromAccount.Id);
+ var updatedTo = await _accountRepository.GetAsync(toAccount.Id);
+
+ updatedFrom.Balance.ShouldBe(800m);
+ updatedTo.Balance.ShouldBe(700m);
+ }
+}
+```
+
+---
+
+## When NOT to Use a Domain Service
+
+Not every operation needs a domain service. Avoid over-engineering:
+
+1. **Simple CRUD Operations**: Use Application Services directly
+2. **Single Aggregate Operations**: Use Entity methods
+3. **Infrastructure Concerns**: Use Infrastructure Services
+4. **Application Workflow**: Use Application Services
+
+```csharp
+// Don't create a domain service for this ❌
+public class AccountBalanceReader : DomainService
+{
+ public decimal GetBalance(Account account) => account.Balance;
+}
+
+// Just use the property directly ✅
+var balance = account.Balance;
+```
+
+---
+
+## Summary
+- **Domain Services** are domain-level, not application-level
+- They encapsulate **business logic that doesn't belong to a single entity**
+- They keep your **entities clean** and **business logic consistent**
+- In ABP, inherit from `DomainService` to get built-in features
+- Keep them **focused**, **pure**, and **testable**
+
+---
+
+## Final Thoughts
+
+Next time you're writing a business rule that doesn't clearly belong to an entity, ask yourself:
+
+> "Is this a Domain Service?"
+
+If it's pure domain logic that coordinates multiple entities or implements a business rule, **put it in the domain layer** - your future self (and your team) will thank you.
+
+Domain Services are a powerful tool in your DDD toolkit. Use them wisely to keep your domain model clean, expressive, and maintainable.
+
+---
diff --git a/docs/en/Community-Articles/2025-11-08-what-is-that-domain-service-in-ddd-for-net-developers/summary.md b/docs/en/Community-Articles/2025-11-08-what-is-that-domain-service-in-ddd-for-net-developers/summary.md
new file mode 100644
index 0000000000..a047be4def
--- /dev/null
+++ b/docs/en/Community-Articles/2025-11-08-what-is-that-domain-service-in-ddd-for-net-developers/summary.md
@@ -0,0 +1 @@
+Learn what Domain Services are in Domain-Driven Design and when to use them in .NET projects. This practical guide covers the difference between Domain and Application Services, features real-world examples including money transfers and order processing, and shows how ABP Framework's DomainService base class simplifies implementation with built-in localization, logging, and event publishing.
diff --git a/docs/en/Community-Articles/2025-11-15-Announcing-SSR-Support/article.md b/docs/en/Community-Articles/2025-11-15-Announcing-SSR-Support/article.md
new file mode 100644
index 0000000000..51b28ef18c
--- /dev/null
+++ b/docs/en/Community-Articles/2025-11-15-Announcing-SSR-Support/article.md
@@ -0,0 +1,156 @@
+# Announcing Server-Side Rendering (SSR) Support for ABP Framework Angular Applications
+
+We are pleased to announce that **Server-Side Rendering (SSR)** has become available for ABP Framework Angular applications! This highly requested feature brings major gains in performance, SEO, and user experience to your Angular applications based on ABP Framework.
+
+## What is Server-Side Rendering (SSR)?
+
+Server-Side Rendering refers to an approach which renders your Angular application on the server as opposed to the browser. The server creates the complete HTML for a page and sends it to the client, which can then show the page to the user. This poses many advantages over traditional client-side rendering.
+
+## Why SSR Matters for ABP Angular Applications
+
+### Improved Performance
+- **Quicker visualization of the first contentful paint (FCP)**: Because prerendered HTML is sent over from the server, users will see content quicker.
+- **Better perceived performance**: Even on slower devices, the page will be displaying something sooner.
+- **Less JavaScript parsing time**: For example, the initial page load will not require parsing and executing a large bundle of JavaScript.
+
+### Enhanced SEO
+- **Improved indexing by search engines**: Search engine bots are able to crawl and index your content quicker.
+- **Improved rankings in search**: The quicker the content loads and the easier it is to access, the better your SEO score.
+- **Preview when sharing on social channels**: Rich previews with the appropriate meta tags are generated when sharing links on social platforms.
+
+### Better User Experience
+- **Support for low bandwidth**: Users with slower Internet connections will have a better experience
+- **Progressive enhancement**: Users can start accessing the content before JavaScript has loaded
+- **Better accessibility**: Screen readers and other assistive technologies can access the content immediately
+
+## Getting Started with SSR
+
+### Adding SSR to an Existing Project
+
+You can easily add SSR support to your existing ABP Angular application using the Angular CLI with ABP schematics:
+
+> Adds SSR configuration to your project
+```bash
+ng generate @abp/ng.schematics:ssr-add
+```
+> Short form
+```bash
+ng g @abp/ng.schematics:ssr-add
+```
+If you have multiple projects in your workspace, you can specify which project to add SSR to:
+
+```bash
+ng g @abp/ng.schematics:ssr-add --project=my-project
+```
+
+If you want to skip the automatic installation of dependencies:
+
+```bash
+ng g @abp/ng.schematics:ssr-add --skip-install
+```
+
+## What Gets Configured
+
+When you add SSR to your ABP Angular project, the schematic automatically:
+
+1. **Installs necessary dependencies**: Adds `@angular/ssr` and related packages
+2. **Creates Server Configuration**: Creates `server.ts` and related files
+3. **Updates Project Structure**:
+ - Creates `main.server.ts` to bootstrap the server
+ - Adds `app.config.server.ts` for standalone apps (or `app.module.server.ts` for NgModule apps)
+ - Configures server routes in `app.routes.server.ts`
+4. **Updates Build Configuration**: updates `angular.json` to include:
+ - a `serve-ssr` target for local SSR development
+ - a `prerender` target for static site generation
+ - Proper output paths for browser and server bundles
+
+## Supported Configurations
+
+The ABP SSR schematic supports both modern and legacy Angular build configurations:
+
+### Application Builder (Suggested)
+- The new `@angular-devkit/build-angular:application` builder
+- Optimized for Angular 17+ apps
+- Enhanced performance and smaller bundle sizes
+
+### Server Builder (Legacy)
+- The original `@angular-devkit/build-angular:server` builder
+- Designed for legacy Angular applications
+- Compatible with legacy applications
+
+## Running Your SSR Application
+
+After adding SSR to your project, you can run your application in SSR mode:
+
+```bash
+# Development mode with SSR
+ng serve
+
+# Or specifically target SSR development server
+npm run serve:ssr
+
+# Build for production
+npm run build:ssr
+
+# Preview production build
+npm run serve:ssr:production
+```
+
+## Important Considerations
+
+### Browser-Only APIs
+Some browser APIs are not available on the server. Use platform checks to conditionally execute code:
+
+```typescript
+import { isPlatformBrowser } from '@angular/common';
+import { PLATFORM_ID, inject } from '@angular/core';
+
+export class MyComponent {
+ private platformId = inject(PLATFORM_ID);
+
+ ngOnInit() {
+ if (isPlatformBrowser(this.platformId)) {
+ // Code that uses browser-only APIs
+ console.log('Running in browser');
+ localStorage.setItem('key', 'value');
+ }
+ }
+}
+```
+
+### Storage APIs
+`localStorage` and `sessionStorage` are not accessible on the server. Consider using:
+- Cookies for server-accessible data.
+- The state transfer API for hydration.
+- ABP's built-in storage abstractions.
+
+### Third-Party Libraries
+Please ensure that any third-party libraries you use are compatible with SSR. These libraries can require:
+- Dynamic imports for browser-only code.
+- Platform-specific service providers.
+- Custom Angular Universal integration.
+
+## ABP Framework Integration
+
+The SSR implementation is natively integrated with all of the ABP Framework features:
+
+- **Authentication & Authorization**: The OAuth/OpenID Connect flow functions seamlessly with ABP
+- **Multi-tenancy**: Fully supports tenant resolution and switching
+- **Localization**: Server-side rendering respects the locale
+- **Permission Management**: Permission checks work on both server and client
+- **Configuration**: The ABP configuration system is SSR-ready
+## Performance Tips
+
+1. **Utilize State Transfer**: Send data from server to client to eliminate redundant HTTP requests
+2. **Optimize Images**: Proper image loading strategies, such as lazy loading and responsive images.
+3. **Cache API Responses**: At the server, implement proper caching strategies.
+4. **Monitor Bundle Size**: Keep your server bundle optimized
+5. **Use Prerendering**: The prerender target should be used for static content.
+
+## Conclusion
+
+Server-side rendering can be a very effective feature in improving your ABP Angular application's performance, SEO, and user experience. Our new SSR schematic will make it easier than ever to add SSR to your project.
+
+Try it today and let us know what you think!
+
+---
diff --git a/docs/en/Community-Articles/2025-11-15-building-an-api-key-management-system/coverimage.png b/docs/en/Community-Articles/2025-11-15-building-an-api-key-management-system/coverimage.png
new file mode 100644
index 0000000000..b4f2222acd
Binary files /dev/null and b/docs/en/Community-Articles/2025-11-15-building-an-api-key-management-system/coverimage.png differ
diff --git a/docs/en/Community-Articles/2025-11-15-building-an-api-key-management-system/images/auth-flow.svg b/docs/en/Community-Articles/2025-11-15-building-an-api-key-management-system/images/auth-flow.svg
new file mode 100644
index 0000000000..0ae07fec22
--- /dev/null
+++ b/docs/en/Community-Articles/2025-11-15-building-an-api-key-management-system/images/auth-flow.svg
@@ -0,0 +1,70 @@
+
diff --git a/docs/en/Community-Articles/2025-11-15-building-an-api-key-management-system/post.md b/docs/en/Community-Articles/2025-11-15-building-an-api-key-management-system/post.md
new file mode 100644
index 0000000000..87dc698b1d
--- /dev/null
+++ b/docs/en/Community-Articles/2025-11-15-building-an-api-key-management-system/post.md
@@ -0,0 +1,354 @@
+# Building an API Key Management System with ABP Framework
+
+API keys are one of the most common authentication methods for APIs, especially for machine-to-machine communication. In this article, I'll explain what API key authentication is, when to use it, and how to implement a complete API key management system using ABP Framework.
+
+## What is API Key Authentication?
+
+An API key is a unique identifier used to authenticate requests to an API. Unlike user credentials (username/password) or OAuth tokens, API keys are designed for:
+
+- **Programmatic access** - Scripts, CLI tools, and automated processes
+- **Service-to-service communication** - Microservices authenticating with each other
+- **Third-party integrations** - External systems accessing your API
+- **IoT devices** - Embedded systems with limited authentication capabilities
+- **Mobile/Desktop apps** - Native applications that need persistent authentication
+
+## Why Use API Keys?
+
+While modern authentication methods like OAuth2 and JWT are excellent for user authentication, API keys offer distinct advantages in certain scenarios:
+
+**Simplicity**: No complex OAuth flows or token refresh mechanisms. Just include the key in your request header.
+
+**Long-lived**: Unlike JWT tokens that expire in minutes/hours, API keys can remain valid for months or years, making them ideal for automated systems.
+
+**Revocable**: You can instantly revoke a compromised key without affecting user credentials.
+
+**Granular Control**: Different keys for different purposes (read-only, admin, specific services).
+
+## Real-World Use Cases
+
+Here are some practical scenarios where API key authentication shines:
+
+### 1. Mobile Applications
+Your mobile app needs to call your backend APIs. Instead of storing user credentials or managing token refresh flows, use an API key.
+
+```csharp
+// Mobile app configuration
+var apiClient = new ApiClient("https://api.yourapp.com");
+apiClient.SetApiKey("sk_mobile_prod_abc123...");
+```
+
+### 2. Microservice Communication
+Service A needs to call Service B's protected endpoints.
+
+```csharp
+// Order Service calling Inventory Service
+var request = new HttpRequestMessage(HttpMethod.Get, "https://inventory-service/api/products");
+request.Headers.Add("X-Api-Key", _configuration["InventoryService:ApiKey"]);
+```
+
+### 3. Third-Party Integrations
+You're providing APIs to external partners or customers.
+
+```bash
+# Customer's integration script
+curl -H "X-Api-Key: pk_partner_xyz789..." \
+ https://api.yourplatform.com/api/orders
+```
+
+## Implementing API Key Management in ABP Framework
+
+Now let's see how to build a complete API key management system using ABP Framework. I've created an open-source implementation that you can use in your projects.
+
+### Project Overview
+
+The implementation consists of:
+
+- **User-based API keys** - Each key belongs to a specific user
+- **Permission delegation** - Keys inherit user permissions with optional restrictions
+- **Secure storage** - Keys are hashed with SHA-256
+- **Prefix-based lookup** - Fast key resolution with caching
+- **Web UI** - Manage keys through a user-friendly interface
+- **Multi-tenancy support** - Full ABP multi-tenancy compatibility
+
+
+
+### Architecture Overview
+
+The solution follows ABP's modular architecture with four main layers:
+
+```
+┌─────────────────────────────────────────────┐
+│ Web Layer (UI) │
+│ • Razor Pages for CRUD operations │
+│ • JavaScript for client interactions │
+└─────────────────────────────────────────────┘
+ ↓
+┌─────────────────────────────────────────────┐
+│ AspNetCore Layer (Middleware) │
+│ • Authentication Handler │
+│ • API Key Resolver (Header/Query) │
+└─────────────────────────────────────────────┘
+ ↓
+┌─────────────────────────────────────────────┐
+│ Application Layer (Business Logic) │
+│ • ApiKeyAppService (CRUD operations) │
+│ • DTO mappings and validations │
+└─────────────────────────────────────────────┘
+ ↓
+┌─────────────────────────────────────────────┐
+│ Domain Layer (Core Business) │
+│ • ApiKey Entity & Manager │
+│ • IApiKeyRepository │
+│ • Domain services & events │
+└─────────────────────────────────────────────┘
+```
+
+### Key Components
+
+#### 1. Domain Layer - The Core Entity
+
+```csharp
+public class ApiKey : FullAuditedAggregateRoot, IMultiTenant
+{
+ public virtual Guid? TenantId { get; protected set; }
+ public virtual Guid UserId { get; protected set; }
+ public virtual string Name { get; protected set; }
+ public virtual string Prefix { get; protected set; }
+ public virtual string KeyHash { get; protected set; }
+ public virtual DateTime? ExpiresAt { get; protected set; }
+ public virtual bool IsActive { get; protected set; }
+
+ // Key format: {prefix}_{key}
+ // Only the hash is stored, never the actual key
+}
+```
+
+**Key Design Decisions:**
+
+- **Prefix-based lookup**: Keys have format `prefix_actualkey`. The prefix is indexed for fast database lookups.
+- **SHA-256 hashing**: The actual key is hashed and never stored in plain text.
+- **User association**: Each key belongs to a user, inheriting their permissions.
+- **Soft delete**: Deleted keys are marked as deleted but not removed from database for audit purposes.
+
+#### 2. Authentication Flow
+
+Here's how authentication works when a request arrives:
+
+
+
+```csharp
+// 1. Extract API key from request
+var apiKey = httpContext.Request.Headers["X-Api-Key"].FirstOrDefault();
+if (string.IsNullOrEmpty(apiKey)) return AuthenticateResult.NoResult();
+
+// 2. Split prefix and key
+var parts = apiKey.Split('_', 2);
+var prefix = parts[0];
+var key = parts[1];
+
+// 3. Find key by prefix (cached)
+var apiKeyEntity = await _apiKeyRepository.FindByPrefixAsync(prefix);
+if (apiKeyEntity == null) return AuthenticateResult.Fail("Invalid API key");
+
+// 4. Verify hash
+var keyHash = HashHelper.ComputeSha256(key);
+if (apiKeyEntity.KeyHash != keyHash)
+ return AuthenticateResult.Fail("Invalid API key");
+
+// 5. Check expiration and active status
+if (apiKeyEntity.ExpiresAt < DateTime.UtcNow || !apiKeyEntity.IsActive)
+ return AuthenticateResult.Fail("API key expired or inactive");
+
+// 6. Create claims principal with user identity
+var claims = new List
+{
+ new Claim(AbpClaimTypes.UserId, apiKeyEntity.UserId.ToString()),
+ new Claim(AbpClaimTypes.TenantId, apiKeyEntity.TenantId?.ToString() ?? ""),
+ new Claim("ApiKeyId", apiKeyEntity.Id.ToString())
+};
+
+return AuthenticateResult.Success(ticket);
+```
+
+#### 3. Creating and Managing API Keys
+
+**Creating a new key:**
+
+
+
+```csharp
+public class ApiKeyManager : DomainService
+{
+ public async Task<(ApiKey, string)> CreateAsync(
+ Guid userId,
+ string name,
+ DateTime? expiresAt = null)
+ {
+ // Generate unique prefix
+ var prefix = await GenerateUniquePrefixAsync();
+
+ // Generate secure random key
+ var key = GenerateSecureRandomString(32);
+
+ // Hash the key for storage
+ var keyHash = HashHelper.ComputeSha256(key);
+
+ var apiKey = new ApiKey(
+ GuidGenerator.Create(),
+ userId,
+ name,
+ prefix,
+ keyHash,
+ expiresAt,
+ CurrentTenant.Id
+ );
+
+ await _apiKeyRepository.InsertAsync(apiKey);
+
+ // Return both entity and the full key (prefix_key)
+ // This is the ONLY time the actual key is visible
+ return (apiKey, $"{prefix}_{key}");
+ }
+}
+```
+
+**Important**: The actual key is returned only once during creation. After that, only the hash is stored.
+
+
+
+### Using API Keys in Your Application
+
+Once created, clients can use the API key to authenticate:
+
+**HTTP Header (Recommended):**
+```bash
+curl -H "X-Api-Key: sk_prod_abc123def456..." \
+ https://api.example.com/api/products
+```
+
+**JavaScript:**
+```javascript
+const response = await fetch('https://api.example.com/api/products', {
+ headers: {
+ 'X-Api-Key': 'sk_prod_abc123def456...'
+ }
+});
+```
+
+**C# HttpClient:**
+```csharp
+var client = new HttpClient();
+client.DefaultRequestHeaders.Add("X-Api-Key", "sk_prod_abc123def456...");
+var response = await client.GetAsync("https://api.example.com/api/products");
+```
+
+**Python:**
+```python
+import requests
+
+headers = {'X-Api-Key': 'sk_prod_abc123def456...'}
+response = requests.get('https://api.example.com/api/products', headers=headers)
+```
+
+### Permission Management
+
+API keys inherit the user's permissions, but you can further restrict them:
+
+
+
+This allows scenarios like:
+- Read-only API key for reporting tools
+- Limited scope keys for third-party integrations
+- Service-specific keys with minimal permissions
+
+```csharp
+// Check if current request is authenticated via API key
+if (CurrentUser.FindClaim("ApiKeyId") != null)
+{
+ var apiKeyId = CurrentUser.FindClaim("ApiKeyId").Value;
+ // Additional API key specific logic
+}
+```
+
+## Performance Considerations
+
+The implementation uses several optimizations:
+
+**1. Prefix-based indexing**: Database lookups are done by prefix (indexed column), not the full key hash.
+
+**2. Distributed caching**: API keys are cached after first lookup, dramatically reducing database queries.
+
+```csharp
+// Cache configuration
+Configure(options =>
+{
+ options.KeyPrefix = "ApiKey:";
+});
+```
+
+**3. Cache invalidation**: When a key is modified or deleted, cache is automatically invalidated.
+
+**Typical Performance:**
+- Cached lookup: **< 5ms**
+- Database lookup: **< 50ms**
+- Cache hit rate: **~95%**
+
+## Security Best Practices
+
+When implementing API key authentication, follow these guidelines:
+
+✅ **Always use HTTPS** - Never send API keys over unencrypted connections
+
+✅ **Use different keys per environment** - Separate keys for dev, staging, production
+
+❌ **Don't log the full key** - Only log the prefix for debugging
+
+## Getting Started
+
+The complete source code is available on GitHub:
+
+**Repository**: [github.com/salihozkara/AbpApikeyManagement](https://github.com/salihozkara/AbpApikeyManagement)
+
+To integrate it into your ABP project:
+
+1. Clone or download the repository
+2. Add project references to your solution
+3. Add module dependencies to your modules
+4. Run EF Core migrations to create the database tables
+5. Navigate to `/ApiKeyManagement` to start managing keys
+
+```csharp
+// In your Web module
+[DependsOn(typeof(ApiKeyManagementWebModule))]
+public class YourWebModule : AbpModule
+{
+ // ...
+}
+
+// In your HttpApi.Host module
+[DependsOn(typeof(ApiKeyManagementHttpApiModule))]
+public class YourHttpApiHostModule : AbpModule
+{
+ // ...
+}
+```
+
+## Conclusion
+
+API key authentication remains a crucial part of modern API security, especially for machine-to-machine communication. While it shouldn't replace user authentication methods like OAuth2 for user-facing applications, it's perfect for:
+
+- Automated scripts and tools
+- Service-to-service communication
+- Third-party integrations
+- Long-lived access without token refresh complexity
+
+The implementation shown here demonstrates how ABP Framework's modular architecture, DDD principles, and built-in features (multi-tenancy, caching, permissions) can be leveraged to build a production-ready API key management system.
+
+The solution is open-source and ready to be integrated into your ABP projects. Feel free to explore the code, suggest improvements, or adapt it to your specific needs.
+
+**Resources:**
+- GitHub Repository: [salihozkara/AbpApikeyManagement](https://github.com/salihozkara/AbpApikeyManagement)
+- ABP Framework: [abp.io](https://abp.io)
+- ABP Documentation: [docs.abp.io](https://abp.io/docs/latest)
+
+Happy coding! 🚀
diff --git a/docs/en/Community-Articles/2025-11-15-building-an-api-key-management-system/summary.md b/docs/en/Community-Articles/2025-11-15-building-an-api-key-management-system/summary.md
new file mode 100644
index 0000000000..4e5abcd224
--- /dev/null
+++ b/docs/en/Community-Articles/2025-11-15-building-an-api-key-management-system/summary.md
@@ -0,0 +1 @@
+Learn how to implement API key authentication in ABP Framework applications. This comprehensive guide covers what API keys are, when to use them over OAuth2/JWT, real-world use cases for mobile apps and microservices, and a complete implementation with user-based key management, SHA-256 hashing, permission delegation, and built-in UI.
diff --git a/docs/en/Community-Articles/2025-11-17-Angular-21-Signals/cover-image.png b/docs/en/Community-Articles/2025-11-17-Angular-21-Signals/cover-image.png
new file mode 100644
index 0000000000..a37bb3d775
Binary files /dev/null and b/docs/en/Community-Articles/2025-11-17-Angular-21-Signals/cover-image.png differ
diff --git a/docs/en/Community-Articles/2025-11-17-Angular-21-Signals/post.md b/docs/en/Community-Articles/2025-11-17-Angular-21-Signals/post.md
new file mode 100644
index 0000000000..60fcc6405b
--- /dev/null
+++ b/docs/en/Community-Articles/2025-11-17-Angular-21-Signals/post.md
@@ -0,0 +1,322 @@
+# Signal-Based Forms in Angular 21: Why You’ll Never Miss Reactive Forms Again
+
+Angular 21 introduces one of the most exciting developments in the modern edition of Angular: **Signal-Based Forms**. Built directly on the reactive foundation of Angular signals, this new experimental API provides a cleaner, more intuitive, strongly typed, and ergonomic approach for managing form state—without the heavy boilerplate of Reactive Forms.
+
+> ⚠️ **Important:** Signal Forms are *experimental*.
+> Their API can change. Avoid using them in critical production scenarios unless you understand the risks.
+
+Despite this, Signal Forms clearly represent Angular’s future direction.
+---
+
+## Why Signal Forms?
+
+Traditionally in Angular, building forms has involved several concerns:
+
+- Tracking values
+- Managing UI interaction states (touched, dirty)
+- Handling validation
+- Keeping UI and model in sync
+
+Reactive Forms solved many challenges but introduced their own:
+
+- Verbosity FormBuilder API
+- Required subscriptions (valueChanges)
+- Manual cleaning
+- Difficult nested forms
+- Weak type-safety
+
+**Signal Forms solve these problems through:**
+
+1." Automatic synchronization
+2." Full type safety
+3." Schema-based validation
+4." Fine-grained reactivity
+5." Drastically reduced boilerplate
+6." Natural integration with Angular Signals
+
+---
+
+### 1. Form Models — The Core of Signal Forms
+
+A **form model** is simply a writable signal holding the structure of your form data.
+
+```ts
+import { Component, signal } from '@angular/core';
+import { form, Field } from '@angular/forms/signals';
+
+@Component({
+ selector: 'app-login',
+ imports: [Field],
+ template: `
+
+
+ `,
+})
+export class LoginComponent {
+ loginModel = signal({
+ email: '',
+ password: '',
+ });
+
+ loginForm = form(this.loginModel);
+}
+```
+
+Calling `form(model)` creates a **Field Tree** that maps directly to your model.
+
+---
+
+### 2. Achieving Full Type Safety
+
+Although TypeScript can infer types from object literals, defining explicit interfaces provides maximum safety and better IDE support.
+
+```ts
+interface LoginData {
+ email: string;
+ password: string;
+}
+
+loginModel = signal({
+ email: '',
+ password: '',
+});
+
+loginForm = form(loginModel);
+```
+
+Now:
+
+- `loginForm.email` → `FieldTree`
+- Accessing invalid fields like `loginForm.username` results in compile-time errors
+
+This level of type safety surpasses Reactive Forms.
+
+---
+
+### 3. Reading Form Values
+
+#### Read from the model (entire form):
+
+```ts
+onSubmit() {
+ const data = this.loginModel();
+ console.log(data.email, data.password);
+}
+```
+
+#### Read from an individual field:
+
+```html
+
Current email: {{ loginForm.email().value() }}
+```
+
+Each field exposes:
+
+- `value()`
+- `valid()`
+- `errors()`
+- `dirty()`
+- `touched()`
+
+All as signals.
+
+---
+
+### 4. Updating Form Models Programmatically
+
+Signal Forms allow three update methods.
+
+#### 1. Replace the entire model
+
+```ts
+this.userModel.set({
+ name: 'Alice',
+ email: 'alice@example.com',
+});
+```
+
+#### 2. Patch specific fields
+
+```ts
+this.userModel.update(prev => ({
+ ...prev,
+ email: newEmail,
+}));
+```
+
+#### 3. Update a single field
+
+```ts
+this.userForm.email().value.set('');
+```
+
+This eliminates the need for:
+
+- `patchValue()`
+- `setValue()`
+- `formGroup.get('field')`
+
+---
+
+### 5. Automatic Two-Way Binding With `[field]`
+
+The `[field]` directive enables perfect two-way data binding:
+
+```html
+
+```
+
+#### How it works:
+
+- **User input → Field state → Model**
+- **Model updates → Field state → Input UI**
+
+No subscriptions.
+No event handlers.
+No boilerplate.
+
+Reactive Forms could never achieve this cleanly.
+
+---
+
+### 6. Nested Models and Arrays
+
+Models can contain nested object structures:
+
+```ts
+userModel = signal({
+ name: '',
+ address: {
+ street: '',
+ city: '',
+ },
+});
+```
+
+Access fields easily:
+
+```html
+
+```
+
+Arrays are also supported:
+
+```ts
+orderModel = signal({
+ items: [
+ { product: '', quantity: 1, price: 0 }
+ ]
+});
+```
+
+Field state persists even when array items move, thanks to identity tracking.
+
+---
+
+### 7. Schema-Based Validation
+
+Validation is clean and centralized:
+
+```ts
+import { required, email } from '@angular/forms/signals';
+
+const model = signal({ email: '' });
+
+const formRef = form(model, {
+ email: [required(), email()],
+});
+```
+
+Field validation state is reactive:
+
+```ts
+formRef.email().valid()
+formRef.email().errors()
+formRef.email().touched()
+```
+
+Validation no longer scatters across components.
+
+---
+
+### 8. When Should You Use Signal Forms?
+
+#### New Angular 21+ apps
+Signal-first architecture is the new standard.
+
+#### Teams wanting stronger type safety
+Every field is exactly typed.
+
+#### Devs tired of Reactive Form boilerplate
+Signal Forms drastically simplify code.
+
+#### Complex UI with computed reactive form state
+Signals integrate perfectly.
+
+#### ❌ Avoid if:
+- You need long-term stability
+- You rely on mature Reactive Forms features
+- Your app must avoid experimental APIs
+
+---
+
+### 9. Reactive Forms vs Signal Forms
+
+| Feature | Reactive Forms | Signal Forms |
+|--------|----------------|--------------|
+| Boilerplate | High | Very low |
+| Type-safety | Weak | Strong |
+| Two-way binding | Manual | Automatic |
+| Validation | Scattered | Centralized schema |
+| Nested forms | Verbose | Natural |
+| Subscriptions | Required | None |
+| Change detection | Zone-heavy | Fine-grained |
+
+Signal Forms feel like the "modern Angular mode," while Reactive Forms increasingly feel legacy.
+
+---
+
+### 10. Full Example: Login Form
+
+```ts
+@Component({
+ selector: 'app-login',
+ imports: [Field],
+ template: `
+
+ `,
+})
+export class LoginComponent {
+ model = signal({ email: '', password: '' });
+ form = form(this.model);
+
+ submit() {
+ console.log(this.model());
+ }
+}
+```
+
+Minimal. Reactive. Completely type-safe.
+
+---
+
+## **Conclusion**
+
+Signal Forms in Angular 21 represent a big step forward:
+
+- Cleaner API
+- Stronger type safety
+- Automatic two-way binding
+- Centralized validation
+- Fine-grained reactivity
+- Dramatically better developer experience
+
+
+Although these are experimental, they clearly show the future of Angular's form ecosystem.
+Once you get into using Signal Forms, you may never want to use Reactive Forms again.
+
+---
diff --git a/docs/en/Community-Articles/2025-11-19-ABP-BLACK-FRIDAY-BLOG/post.md b/docs/en/Community-Articles/2025-11-19-ABP-BLACK-FRIDAY-BLOG/post.md
new file mode 100644
index 0000000000..153470666f
--- /dev/null
+++ b/docs/en/Community-Articles/2025-11-19-ABP-BLACK-FRIDAY-BLOG/post.md
@@ -0,0 +1,25 @@
+**ABP Black Friday Deals are Almost Here\!**
+
+The season of huge savings is back\! We are happy to announce **ABP Black Friday Campaign**, packed with exclusive deals that you simply won't want to miss. Whether you are ready to start building with ABP or looking to expand your existing license, this is your chance to maximize your savings\!
+
+**Campaign Dates: Mark Your Calendar**
+
+Black Friday campaign is live for one week only\! Our deals run from: **November 24th \- December 1st.**
+
+Don't miss this limited-time opportunity to **save up to $3,000** and take your software development to the next level.
+
+**What's Included in the ABP Black Friday Campaign?**
+
+Here’s why this campaign is the best time to buy or upgrade:
+
+* Open to Everyone: This campaign is available for both new and existing customers.
+* Stack Your Savings: You can combine this Black Friday offer with our multi-year discounts for the greatest possible value.
+* Flexible Upgrades: Planning to upgrade to a higher package? Now is the perfect time to make that move at a lower cost.
+* More Developer Seats? No Problem\! Additional developer seats are also eligible under this campaign, allowing you to grow your team effortlessly and affordably.
+
+**Save Money Now\!**
+
+This campaign is your best opportunity all year to unlock advanced features, scale your team, or upgrade your plan while **saving up to $3,000.** Secure your savings before the campaign ends on December 1st\!
+
+[**Visit Pricing Page to Explore Offers\!**](https://abp.io/pricing)
+
diff --git a/docs/en/Community-Articles/2025-11-20-Whats-New-In-NET10-Libraries-Runtime/Post.md b/docs/en/Community-Articles/2025-11-20-Whats-New-In-NET10-Libraries-Runtime/Post.md
new file mode 100644
index 0000000000..4346346e7e
--- /dev/null
+++ b/docs/en/Community-Articles/2025-11-20-Whats-New-In-NET10-Libraries-Runtime/Post.md
@@ -0,0 +1,149 @@
+# What’s New in .NET 10 Libraries and Runtime?
+
+With .NET 10, Microsoft continues to evolve the platform toward higher performance, stronger security, and modern developer ergonomics. This release brings substantial updates across both the **.NET Libraries** and the **.NET Runtime**, making everyday development faster, safer, and more efficient.
+
+
+
+------
+
+## .NET Libraries Improvements
+
+### 1. Post-Quantum Cryptography
+
+.NET 10 introduces support for new **quantum-resistant algorithms**, ML-KEM, ML-DSA, and SLH-DSA, through the `System.Security.Cryptography` namespace.
+ These are available when running on compatible OS versions (OpenSSL 3.5+ or Windows CNG).
+
+**Why it matters:** This future-proofs .NET apps against next-generation security threats, keeping them aligned with emerging FIPS standards and PQC readiness.
+
+
+
+------
+
+### 2. Numeric Ordering for String Comparison
+
+The `StringComparer` and `HashSet` classes now support **numeric-aware string comparison** via `CompareOptions.NumericOrdering`.
+ This allows natural sorting of strings like `v2`, `v10`, `v100`.
+
+**Why it matters:** Cleaner and more intuitive sorting for version names, product codes, and other mixed string-number data.
+
+
+
+------
+
+### 3. String Normalization for Spans
+
+Normalization APIs now support `Span` and `ReadOnlySpan`, enabling text normalization without creating new string objects.
+
+**Why it matters:** Lower memory allocations in text-heavy scenarios, perfect for parsers, libraries, and streaming data pipelines.
+
+
+
+------
+
+### 4. UTF-8 Support for Hex String Conversion
+
+The `Convert` class now allows **direct UTF-8 to hex conversions**, eliminating the need for intermediate string allocations.
+
+**Why it matters:** Faster serialization and deserialization, especially useful in networking, cryptography, and binary protocols.
+
+
+
+------
+
+### 5. Async ZIP APIs
+
+ZIP handling now fully supports asynchronous operations, from creation and extraction to updates, with cancellation support.
+
+**Why it matters:** Ideal for real-time applications, WebSocket I/O, and microservices that handle compressed data streams.
+
+
+
+------
+
+### 6. ZipArchive Performance Boost
+
+ZIP operations are now faster and more memory-efficient thanks to parallel extraction and reduced memory pressure.
+
+**Why it matters:** Perfect for file-heavy workloads like installers, packaging tools, and CI/CD utilities.
+
+------
+
+
+
+### 7. TLS 1.3 Support on macOS
+
+.NET 10 brings **TLS 1.3 client support** to macOS using Apple’s `Network.framework`, integrated with `SslStream` and `HttpClient`.
+
+**Why it matters:** Consistent, faster, and more secure HTTPS connections across Windows, Linux, and macOS.
+
+
+
+------
+
+### 8. Telemetry Schema URLs
+
+`ActivitySource` and `Meter` now support **telemetry schema URLs**, aligning with OpenTelemetry standards.
+
+**Why it matters:** Simplifies integration with observability platforms like Grafana, Prometheus, and Application Insights.
+
+
+
+------
+
+### 9. OrderedDictionary Performance Improvements
+
+New overloads for `TryAdd` and `TryGetValue` improve performance by returning entry indexes directly.
+
+**Why it matters:** Up to 20% faster JSON updates and more efficient dictionary operations, particularly in `JsonObject`.
+
+
+
+------
+
+## .NET Runtime Improvements
+
+
+
+### 1. JIT Compiler Enhancements
+
+- **Faster Struct Handling:** The JIT now passes structs directly via CPU registers, reducing memory operations.
+ *→ Result: Faster execution and tighter loops.*
+
+- **Array Interface Devirtualization:** Loops like `foreach` over arrays are now almost as fast as `for` loops.
+ *→ Result: Fewer abstraction costs and better inlining.*
+
+- **Improved Code Layout:** A new 3-opt heuristic arranges “hot” code paths closer in memory.
+ *→ Result: Better branch prediction and CPU cache performance.*
+
+- **Smarter Inlining:** The JIT can now inline more method types (even with `try-finally`), guided by runtime profiling.
+ *→ Result: Reduced overhead for frequently called methods.*
+
+
+
+------
+
+### 2. Stack Allocation Improvements
+
+.NET 10 extends stack allocation to **small arrays of both value and reference types**, with **escape analysis** ensuring safe allocation.
+
+**Why it matters:** Fewer heap allocations mean less GC work and faster execution, especially in high-frequency or temporary operations.
+
+
+
+------
+
+### 3. ARM64 Write-Barrier Optimization
+
+The garbage collector’s write-barrier logic is now optimized for ARM64, cutting unnecessary memory scans.
+
+**Why it matters:** Up to **20% shorter GC pauses** and better overall performance on ARM-based devices and servers.
+
+
+
+
+
+## Summary
+
+.NET 10 doubles down on **performance, efficiency, and modern standards**. From quantum-ready cryptography to smarter memory management and diagnostics, this release makes .NET more ready than ever for the next generation of applications.
+
+Whether you’re building enterprise APIs, distributed systems, or cloud-native tools, upgrading to .NET 10 means faster code, safer systems, and better developer experience.
diff --git a/docs/en/Community-Articles/2025-11-21-AntiGravity/Post.md b/docs/en/Community-Articles/2025-11-21-AntiGravity/Post.md
new file mode 100644
index 0000000000..d5e34e7892
--- /dev/null
+++ b/docs/en/Community-Articles/2025-11-21-AntiGravity/Post.md
@@ -0,0 +1,158 @@
+# My First Look and Experience with Google AntiGravity
+
+## Is Google AntiGravity Going to Replace Your Main Code Editor?
+
+Today, I tried the new code-editor AntiGravity by Google. *"It's beyond a code-editor*" by Google 🙄
+When I first launch it, I see the UI is almost same as Cursor. They're both based on Visual Studio Code.
+That's why it was not hard to find what I'm looking for.
+
+First of all, the main difference as I see from the Cursor is; when I type a prompt in the agent section **AntiGravity first creates a Task List** (like a road-map) and whenever it finishes a task, it checks the corresponding task. Actually Cursor has a similar functionality but AntiGravity took it one step further.
+
+Second thing which was good to me; AntiGravity uses [Nano Banana 🍌](https://gemini.google/tr/overview/image-generation/). This is Google's AI image generation model... Why it's important because when you create an app, you don't need to search for graphics, deal with image licenses. **AntiGravity generates images automatically and no license is required!**
+
+Third exciting feature for me; **AntiGravity is integrated with Google Chrome and can communicate with the running website**. When I first run my web project, it installed a browser extension which can see and interact with my website. It can see the results, click somewhere else on the page, scroll, fill up the forms, amazing 😵
+
+Another feature I loved is that **you can enter a new prompt even while AntiGravity is still generating a response** 🧐. It instantly prioritizes the latest input and adjusts the ongoing process if needed. But in Cursor, if you add a prompt before the cursor finishes, it simply queues it and runs it later 😔.
+
+And lastly, **AntiGravity is working very good with Gemini 3**.
+
+Well, everything was not so perfect 😥 When I tried AntiGravity, couple of times it stucked AI generation and Agent stopped. I faced errors like this 👇
+
+
+
+
+
+## Debugging .NET Projects via AntiGravity
+
+⚠ There's a crucial development issue with AntiGravity (and also for Cursor, Windsurf etc...) 🤕 you **cannot debug your .NET application with AntiGravity 🥺.** *This is Microsoft's policy!* Microsoft doesn't allow debugging for 3rd party IDEs and shows the below error... That's why I cannot say it's a downside of AntiGravity. You need to use Microsft's original VS Code, Visual Studio or Rider for debugging. But wait a while there's a workaround for this, I'll let you know in the next section.
+
+
+
+
+
+### What does this error mean?
+
+AntiGravity, Cursor, Windsurf etc... are using Visual Studio Code and the C# extension for VS Code includes the Microsoft .NET Core Debugger "*vsdbg*".
+VS Code is open-source but "*vsdbg*" is not open-source! It's working only with Visual Studio Code, Visual Studio and Visual Studio for Mac. This is clearly stated at [Microsoft's this link](https://github.com/dotnet/vscode-csharp/blob/main/docs/debugger/Microsoft-.NET-Core-Debugger-licensing-and-Microsoft-Visual-Studio-Code.md).
+
+### Ok! How to resolve debugging issue with AntiGravity? and Cursor and Windsurf...
+
+There's a free C# debugger extension for Visual Studio Code based IDEs that supports AntiGravity, Cursor and Windsurf. The extension name is **C#**.
+You can download this free C# debugger extension at 👉 [open-vsx.org/extension/muhammad-sammy/csharp/](https://open-vsx.org/extension/muhammad-sammy/csharp/).
+For AntiGravity open Extension window (*Ctrl + Shift + X*) and search for `C#`, there you'll see this extension.
+
+
+
+After installing, I restarted AntiGravity and now I can see the red circle which allows me to add breakpoint on C# code.
+
+
+
+### Another Extension For Debugging .NET Apps on VS Code
+
+Recently I heard about DotRush extension from the folks. As they say DotRush works slightly faster and support Razor pages (.cshtml files).
+Here's the link for DotRush https://github.com/JaneySprings/DotRush
+
+### Finding Website Running Port
+
+When you run the web project via C# debugger extension, normally it's not using the `launch.json` therefore the website port is not the one when you start from Visual Studio / Rider... So what's my website's port which I just run now? Normally for ASP.NET Core **the default port is 5000**. You can try navigating to http://localhost:5000/.
+Alternatively you can write the below code in `Program.cs` which prints the full address of your website in the logs.
+If you do the steps which I showed you, you can debug your C# application via AntiGravity and other VS Code derivatives.
+
+
+
+## How Much is AntiGravity? 💲
+
+Currently there's only individual plan is available for personal accounts and that's free 👏! The contents of Team and Enterprise plans and prices are not announced yet. But **Gemini 3 is not free**! I used it with my company's Google Workspace account which we normally pay for Gemini.
+
+
+
+## More About AntiGravity
+
+There have been many AI assisted IDEs like [Windsurf](https://windsurf.com/), [Cursor](https://cursor.com/), [Zed](https://zed.dev/), [Replit](https://replit.com/) and [Fleet](https://www.jetbrains.com/fleet/). But this time it's different, this is backed by Google.
+As you see from the below image AntiGravity, uses a standard grid layout as others based on VS Code editor.
+It's very similar to Cursor, Visual Studio, Rider.
+
+
+
+## Supported LLMs 🧠
+
+Antigravity offers the below models which supports reasoning: Gemini 3 Pro, Claude Sonnet 4.5, GPT-OSS
+
+
+
+Antigravity uses other models for supportive tasks in the background:
+
+- **Nano banana**: This is used to generate images.
+- **Gemini 2.5 Pro UI Checkpoint**: It's for the browser subagent to trigger browser action such as clicking, scrolling, or filling in input.
+- **Gemini 2.5 Flash**: For checkpointing and context summarization, this is used.
+- **Gemini 2.5 Flash Lite**: And when it's need to make a semantic search in your code-base, this is used.
+
+## AntiGravity Can See Your Website
+
+This makes a big difference from traditional IDEs. AntiGravity's browser agent is taking screenshots of your pages when it needs to check. This is achieved by a Chrome Extension as a tool to the agent, and you can also prompt the agent to take a screenshot of a page. It can iterate on website designs and implementations, it can perform UI Testing, it can monitor dashboards, it can automate routine tasks like rerunning CI.
+This is the link for the extension 👉 [chromewebstore.google.com/detail/antigravity-browser-exten/eeijfnjmjelapkebgockoeaadonbchdd](https://chromewebstore.google.com/detail/antigravity-browser-exten/eeijfnjmjelapkebgockoeaadonbchdd). AntiGravity will install this extension automatically on the first run.
+
+
+
+
+
+## MCP Integration
+
+### When Do We Need MCP in a Code Editor?
+
+Simply if we want to connect to a 3rd party service to complete our task we need MCP. So AntiGravity can connect to your DB and write proper SQL queries or it can pull in recent build logs from Netlify or Heroku. Also you can ask AntiGravity to to connect GitHub for finding the best authentication pattern.
+
+### AntiGravity Supports These MCP Servers
+
+Airweave, AlloyDB for PostgreSQL, Atlassian, BigQuery, Cloud SQL for PostgreSQL, Cloud SQL for MySQL, Cloud SQL for SQL Server, Dart, Dataplex, Figma Dev Mode MCP, Firebase, GitHub, Harness, Heroku, Linear, Locofy, Looker, MCP Toolbox for Databases, MongoDB, Neon, Netlify, Notion, PayPal, Perplexity Ask, Pinecone, Prisma, Redis, Sequential Thinking, SonarQube, Spanner, Stripe and Supabase.
+
+
+
+## Agent Settings ⚙️
+
+The major settings of Agent are:
+
+- **Agent Auto Fix Lints**: I enabled this setting because I want the Agent automatically fixes its own mistakes for invalid syntax, bad formatting, unused variables, unreachable code or following coding standards... It makes extra tool calls that's why little bit expensive 🥴.
+- **Auto Execution**: Sometimes Agent tries to build application or writing test code and running it, in these cases it executes command. I choose "Turbo" 🤜 With this option, Agent always runs the terminal command and controls my browser.
+- **Review Policy**: How much control you are giving to agent 🙎. I choose "Always Proceed" 👌 because I mostly trust AI 😀. The Agent will never ask for review.
+
+
+
+## Differences Between Cursor and AntiGravity
+
+While Cursor was the champion of AI code editors, **Antigravity brings a different philosophy**.
+
+### 1. "Agent-First 🤖" vs "You-First 🤠"
+
+- **Cursor:** It acts like an assistant; it predicts your next move, auto-completes your thoughts, and helps you refactor while you type. You are still the driver; Cursor just drives the car at 200 km/h.
+- **Antigravity:** Antigravity is built to let you manage coding tasks. It is "Agent-First." You don't just type code; you assign tasks to autonomous agents (e.g., "Fix the bug in the login flow and verify it in the browser"). It behaves more like a junior developer that you supervise.
+
+### 2. The Interface
+
+- **Cursor:** Looks and feels exactly like **VS Code**. If you know VS Code, you know Cursor.
+
+- **Antigravity:** Introduces 2 major layouts:
+ - **Editor View:** Similar to a standard IDE
+ - **Manager View:** A dashboard where you see multiple "Agents" working in parallel. You can watch them plan, execute, and test tasks asynchronously.
+
+### 3. Verification & Trust
+
+- **Cursor:** You verify by reading the code diffs it suggests.
+- **Antigravity:** Introduces **Artifacts**... Since the agents work autonomously, they generate proof-of-work documents, screenshots of the app running, browser logs and execution plans. So you can verify what they did without necessarily reading every line of code immediately.
+
+### 4. Capabilities
+
+- **Cursor:** Best-in-class **Autocomplete** ("Tab" feature) and **Composer** (multi-file editing). It excels at "Vibe Coding". It's getting into a flow state where the AI writes the boilerplate and you direct the logic.
+- **Antigravity:** Is good at **Autonomous Execution**. It has a built-in browser and terminal that the *Agent* controls. The Agent can write code, run the server, open the browser, see the error, and fix it 😎
+
+### 5. AI Models (Brains 🧠)
+
+- **Cursor:** Model Agnostic. You can switch between **Claude 3.5 Sonnet** *-mostly the community uses this-*, GPT-4o, and others.
+- **Antigravity:** Built deeply around **Gemini 3 Pro**. It leverages Gemini's massive context window (1M+ tokens) to understand huge mono repos without needing as much "RAG" as Cursor.
+
+
+
+## Try It Yourself Now 🤝
+
+If you are ready to experience the new AI code editor by Google, download and use 👇
+[**Launch Google AntiGravity**](https://antigravity.google/)
\ No newline at end of file
diff --git a/docs/en/Community-Articles/2025-11-21-AntiGravity/agent-settings.png b/docs/en/Community-Articles/2025-11-21-AntiGravity/agent-settings.png
new file mode 100644
index 0000000000..a659c244c5
Binary files /dev/null and b/docs/en/Community-Articles/2025-11-21-AntiGravity/agent-settings.png differ
diff --git a/docs/en/Community-Articles/2025-11-21-AntiGravity/anti-gravity-ui.png b/docs/en/Community-Articles/2025-11-21-AntiGravity/anti-gravity-ui.png
new file mode 100644
index 0000000000..885284dd56
Binary files /dev/null and b/docs/en/Community-Articles/2025-11-21-AntiGravity/anti-gravity-ui.png differ
diff --git a/docs/en/Community-Articles/2025-11-21-AntiGravity/breakpoint.png b/docs/en/Community-Articles/2025-11-21-AntiGravity/breakpoint.png
new file mode 100644
index 0000000000..0ef01d71a3
Binary files /dev/null and b/docs/en/Community-Articles/2025-11-21-AntiGravity/breakpoint.png differ
diff --git a/docs/en/Community-Articles/2025-11-21-AntiGravity/cover.png b/docs/en/Community-Articles/2025-11-21-AntiGravity/cover.png
new file mode 100644
index 0000000000..b2ec245a2f
Binary files /dev/null and b/docs/en/Community-Articles/2025-11-21-AntiGravity/cover.png differ
diff --git a/docs/en/Community-Articles/2025-11-21-AntiGravity/csharp-debug-extension.png b/docs/en/Community-Articles/2025-11-21-AntiGravity/csharp-debug-extension.png
new file mode 100644
index 0000000000..6807c3f6bc
Binary files /dev/null and b/docs/en/Community-Articles/2025-11-21-AntiGravity/csharp-debug-extension.png differ
diff --git a/docs/en/Community-Articles/2025-11-21-AntiGravity/debug.png b/docs/en/Community-Articles/2025-11-21-AntiGravity/debug.png
new file mode 100644
index 0000000000..c4674a89f3
Binary files /dev/null and b/docs/en/Community-Articles/2025-11-21-AntiGravity/debug.png differ
diff --git a/docs/en/Community-Articles/2025-11-21-AntiGravity/errors.png b/docs/en/Community-Articles/2025-11-21-AntiGravity/errors.png
new file mode 100644
index 0000000000..f8c2e43dac
Binary files /dev/null and b/docs/en/Community-Articles/2025-11-21-AntiGravity/errors.png differ
diff --git a/docs/en/Community-Articles/2025-11-21-AntiGravity/extension-features.png b/docs/en/Community-Articles/2025-11-21-AntiGravity/extension-features.png
new file mode 100644
index 0000000000..cd0b07cabf
Binary files /dev/null and b/docs/en/Community-Articles/2025-11-21-AntiGravity/extension-features.png differ
diff --git a/docs/en/Community-Articles/2025-11-21-AntiGravity/extension.png b/docs/en/Community-Articles/2025-11-21-AntiGravity/extension.png
new file mode 100644
index 0000000000..601a28849a
Binary files /dev/null and b/docs/en/Community-Articles/2025-11-21-AntiGravity/extension.png differ
diff --git a/docs/en/Community-Articles/2025-11-21-AntiGravity/find-website-port.png b/docs/en/Community-Articles/2025-11-21-AntiGravity/find-website-port.png
new file mode 100644
index 0000000000..183e8c6f5b
Binary files /dev/null and b/docs/en/Community-Articles/2025-11-21-AntiGravity/find-website-port.png differ
diff --git a/docs/en/Community-Articles/2025-11-21-AntiGravity/image-20251123185724281.png b/docs/en/Community-Articles/2025-11-21-AntiGravity/image-20251123185724281.png
new file mode 100644
index 0000000000..82b8f478e1
Binary files /dev/null and b/docs/en/Community-Articles/2025-11-21-AntiGravity/image-20251123185724281.png differ
diff --git a/docs/en/Community-Articles/2025-11-21-AntiGravity/llms.png b/docs/en/Community-Articles/2025-11-21-AntiGravity/llms.png
new file mode 100644
index 0000000000..82b8f478e1
Binary files /dev/null and b/docs/en/Community-Articles/2025-11-21-AntiGravity/llms.png differ
diff --git a/docs/en/Community-Articles/2025-11-21-AntiGravity/mcp.png b/docs/en/Community-Articles/2025-11-21-AntiGravity/mcp.png
new file mode 100644
index 0000000000..06a343f068
Binary files /dev/null and b/docs/en/Community-Articles/2025-11-21-AntiGravity/mcp.png differ
diff --git a/docs/en/Community-Articles/2025-11-21-AntiGravity/pricing.png b/docs/en/Community-Articles/2025-11-21-AntiGravity/pricing.png
new file mode 100644
index 0000000000..0b552352e3
Binary files /dev/null and b/docs/en/Community-Articles/2025-11-21-AntiGravity/pricing.png differ
diff --git a/docs/en/Community-Articles/2025-11-22-building-production-ready-llm-applications/coverimage.png b/docs/en/Community-Articles/2025-11-22-building-production-ready-llm-applications/coverimage.png
new file mode 100644
index 0000000000..b264e259e9
Binary files /dev/null and b/docs/en/Community-Articles/2025-11-22-building-production-ready-llm-applications/coverimage.png differ
diff --git a/docs/en/Community-Articles/2025-11-22-building-production-ready-llm-applications/images/chat-history-hybrid.svg b/docs/en/Community-Articles/2025-11-22-building-production-ready-llm-applications/images/chat-history-hybrid.svg
new file mode 100644
index 0000000000..ab1bb36114
--- /dev/null
+++ b/docs/en/Community-Articles/2025-11-22-building-production-ready-llm-applications/images/chat-history-hybrid.svg
@@ -0,0 +1,114 @@
+
\ No newline at end of file
diff --git a/docs/en/Community-Articles/2025-11-22-building-production-ready-llm-applications/images/mcp-architecture.svg b/docs/en/Community-Articles/2025-11-22-building-production-ready-llm-applications/images/mcp-architecture.svg
new file mode 100644
index 0000000000..ee590d27eb
--- /dev/null
+++ b/docs/en/Community-Articles/2025-11-22-building-production-ready-llm-applications/images/mcp-architecture.svg
@@ -0,0 +1,150 @@
+
\ No newline at end of file
diff --git a/docs/en/Community-Articles/2025-11-22-building-production-ready-llm-applications/images/multilingual-rag.svg b/docs/en/Community-Articles/2025-11-22-building-production-ready-llm-applications/images/multilingual-rag.svg
new file mode 100644
index 0000000000..81173091f0
--- /dev/null
+++ b/docs/en/Community-Articles/2025-11-22-building-production-ready-llm-applications/images/multilingual-rag.svg
@@ -0,0 +1,135 @@
+
\ No newline at end of file
diff --git a/docs/en/Community-Articles/2025-11-22-building-production-ready-llm-applications/images/pgvector-integration.svg b/docs/en/Community-Articles/2025-11-22-building-production-ready-llm-applications/images/pgvector-integration.svg
new file mode 100644
index 0000000000..2903740e57
--- /dev/null
+++ b/docs/en/Community-Articles/2025-11-22-building-production-ready-llm-applications/images/pgvector-integration.svg
@@ -0,0 +1,112 @@
+
\ No newline at end of file
diff --git a/docs/en/Community-Articles/2025-11-22-building-production-ready-llm-applications/images/rag-parent-child.svg b/docs/en/Community-Articles/2025-11-22-building-production-ready-llm-applications/images/rag-parent-child.svg
new file mode 100644
index 0000000000..752c2c42b1
--- /dev/null
+++ b/docs/en/Community-Articles/2025-11-22-building-production-ready-llm-applications/images/rag-parent-child.svg
@@ -0,0 +1,118 @@
+
\ No newline at end of file
diff --git a/docs/en/Community-Articles/2025-11-22-building-production-ready-llm-applications/images/reasoning-effort-diagram.svg b/docs/en/Community-Articles/2025-11-22-building-production-ready-llm-applications/images/reasoning-effort-diagram.svg
new file mode 100644
index 0000000000..fc6a18d68d
--- /dev/null
+++ b/docs/en/Community-Articles/2025-11-22-building-production-ready-llm-applications/images/reasoning-effort-diagram.svg
@@ -0,0 +1,60 @@
+
\ No newline at end of file
diff --git a/docs/en/Community-Articles/2025-11-22-building-production-ready-llm-applications/images/svg-diagram-example.svg b/docs/en/Community-Articles/2025-11-22-building-production-ready-llm-applications/images/svg-diagram-example.svg
new file mode 100644
index 0000000000..6087893702
--- /dev/null
+++ b/docs/en/Community-Articles/2025-11-22-building-production-ready-llm-applications/images/svg-diagram-example.svg
@@ -0,0 +1,149 @@
+
\ No newline at end of file
diff --git a/docs/en/Community-Articles/2025-11-22-building-production-ready-llm-applications/post.md b/docs/en/Community-Articles/2025-11-22-building-production-ready-llm-applications/post.md
new file mode 100644
index 0000000000..8fa2067d01
--- /dev/null
+++ b/docs/en/Community-Articles/2025-11-22-building-production-ready-llm-applications/post.md
@@ -0,0 +1,414 @@
+# Building Production-Ready LLM Applications with .NET: A Practical Guide
+
+Large Language Models (LLMs) have evolved rapidly, and integrating them into production .NET applications requires staying current with the latest approaches. In this article, I'll share practical tips and patterns I've learned while building LLM-powered systems, covering everything from API changes in GPT-5 to implementing efficient RAG (Retrieval Augmented Generation) architectures.
+
+Whether you're building a chatbot, a knowledge base assistant, or integrating AI into your enterprise applications, these production-tested insights will help you avoid common pitfalls and build more reliable systems.
+
+## The Temperature Paradigm Shift: GPT-5 Changes Everything
+
+If you've been working with GPT-4 or earlier models, you're familiar with the `temperature` and `top_p` parameters for controlling response randomness. **Here's the critical update**: GPT-5 no longer supports these parameters!
+
+### The Old Way (GPT-4)
+```csharp
+var chatRequest = new ChatOptions
+{
+ Temperature = 0.7, // ✅ Worked with GPT-4
+ TopP = 0.9 // ✅ Worked with GPT-4
+};
+```
+
+### The New Way (GPT-5)
+```csharp
+var chatRequest = new ChatOptions
+{
+ RawRepresentationFactory = (client => new ChatCompletionOptions()
+ {
+#pragma warning disable OPENAI001
+ ReasoningEffortLevel = "minimal",
+#pragma warning restore OPENAI001
+ })
+};
+```
+
+**Why the change?** GPT-5 incorporates an internal reasoning and verification process. Instead of controlling randomness, you now specify how much computational effort the model should invest in reasoning through the problem.
+
+
+
+### Choosing the Right Reasoning Level
+
+- **Low**: Quick responses for simple queries (e.g., "What's the capital of France?")
+- **Medium**: Balanced approach for most use cases
+- **High**: Complex reasoning tasks (e.g., code generation, multi-step problem solving)
+
+> **Pro Tip**: Reasoning tokens are included in your API costs. Use "High" only when necessary to optimize your budget.
+
+## System Prompts: The "Lost in the Middle" Problem
+
+Here's a critical insight that can save you hours of debugging: **Important rules must be repeated at the END of your prompt!**
+
+### ❌ What Doesn't Work
+```
+You are a helpful assistant.
+RULE: Never share passwords or sensitive information.
+
+[User Input]
+```
+
+### ✅ What Actually Works
+```
+You are a helpful assistant.
+RULE: Never share passwords or sensitive information.
+
+[User Input]
+
+⚠️ REMINDER: Apply the rules above strictly, ESPECIALLY regarding passwords.
+```
+
+**Why?** LLMs suffer from the "Lost in the Middle" phenomenon—they pay more attention to the beginning and end of the context window. Critical instructions buried in the middle are often ignored.
+
+## RAG Architecture: The Parent-Child Pattern
+
+Retrieval Augmented Generation (RAG) is essential for grounding LLM responses in your own data. The most effective pattern I've found is the **Parent-Child approach**.
+
+
+
+### How It Works
+
+1. **Split documents into hierarchies**:
+ - **Parent chunks**: Large sections (1000-2000 tokens) for context
+ - **Child chunks**: Small segments (200-500 tokens) for precise retrieval
+
+2. **Store both in vector database** with references
+
+3. **Query flow**:
+ - Search using child chunks (higher precision)
+ - Return parent chunks to LLM (richer context)
+
+### The Overlap Strategy
+
+Always use overlapping chunks to prevent information loss at boundaries!
+
+```
+Chunk 1: Token 0-500
+Chunk 2: Token 400-900 ← 100 token overlap
+Chunk 3: Token 800-1300 ← 100 token overlap
+```
+
+**Standard recommendation**: 10-20% overlap (for 500 tokens, use 50-100 token overlap)
+
+### Implementation with Semantic Kernel
+
+```csharp
+using Microsoft.SemanticKernel.Text;
+
+var chunks = TextChunker.SplitPlainTextParagraphs(
+ documentText,
+ maxTokensPerParagraph: 500,
+ overlapTokens: 50
+);
+
+foreach (var chunk in chunks)
+{
+ var embedding = await embeddingService.GenerateEmbeddingAsync(chunk);
+ await vectorDb.StoreAsync(chunk, embedding);
+}
+```
+
+## PostgreSQL + pgvector: The Pragmatic Choice
+
+For .NET developers, choosing a vector database can be overwhelming. After evaluating multiple options, **PostgreSQL with pgvector** is the most practical choice for most scenarios.
+
+
+
+### Why pgvector?
+
+✅ **Use existing SQL knowledge** - No new query language to learn
+✅ **EF Core integration** - Works with your existing data access layer
+✅ **JOIN with metadata** - Combine vector search with traditional queries
+✅ **WHERE clause filtering** - Filter by tenant, user, date, etc.
+✅ **ACID compliance** - Transaction support for data consistency
+✅ **No separate infrastructure** - One database for everything
+
+### Setting Up pgvector with EF Core
+
+First, install the NuGet package:
+
+```bash
+dotnet add package Pgvector.EntityFrameworkCore
+```
+
+Define your entity:
+
+```csharp
+using Pgvector;
+using Pgvector.EntityFrameworkCore;
+
+public class DocumentChunk
+{
+ public Guid Id { get; set; }
+ public string Content { get; set; }
+ public Vector Embedding { get; set; } // 👈 pgvector type
+ public Guid ParentChunkId { get; set; }
+ public DateTime CreatedAt { get; set; }
+}
+```
+
+Configure in DbContext:
+
+```csharp
+protected override void OnModelCreating(ModelBuilder builder)
+{
+ builder.HasPostgresExtension("vector");
+
+ builder.Entity()
+ .Property(e => e.Embedding)
+ .HasColumnType("vector(1536)"); // 👈 OpenAI embedding dimension
+
+ builder.Entity()
+ .HasIndex(e => e.Embedding)
+ .HasMethod("hnsw") // 👈 Fast approximate search
+ .HasOperators("vector_cosine_ops");
+}
+```
+
+### Performing Vector Search
+
+```csharp
+using Pgvector.EntityFrameworkCore;
+
+public async Task> SearchAsync(string query)
+{
+ // 1. Convert query to embedding
+ var queryVector = await _embeddingService.GetEmbeddingAsync(query);
+
+ // 2. Search
+ return await _context.DocumentChunks
+ .OrderBy(c => c.Embedding.L2Distance(queryVector)) // 👈 Lower is better
+ .Take(5)
+ .ToListAsync();
+}
+```
+
+**Source**: [Pgvector.NET on GitHub](https://github.com/pgvector/pgvector-dotnet?tab=readme-ov-file#entity-framework-core)
+
+## Smart Tool Usage: Make RAG a Tool, Not a Tax
+
+A common mistake is calling RAG on every single user message. This wastes tokens and money. Instead, **make RAG a tool** and let the LLM decide when to use it.
+
+### ❌ Expensive Approach
+```csharp
+// Always call RAG, even for "Hello"
+var context = await PerformRAG(userMessage);
+var response = await chatClient.CompleteAsync($"{context}\n\n{userMessage}");
+```
+
+### ✅ Smart Approach
+```csharp
+[KernelFunction]
+[Description("Search the company knowledge base for information")]
+public async Task SearchKnowledgeBase(
+ [Description("The search query")] string query)
+{
+ var results = await _vectorDb.SearchAsync(query);
+ return string.Join("\n---\n", results.Select(r => r.Content));
+}
+```
+
+The LLM will call `SearchKnowledgeBase` only when needed:
+- "Hello" → No tool call
+- "What was our 2024 revenue?" → Calls tool
+- "Tell me a joke" → No tool call
+
+## Multilingual RAG: Query Translation Strategy
+
+When your documents are in one language (e.g., English) but users query in another (e.g., Turkish), you need a translation strategy.
+
+
+
+### Solution Options
+
+**Option 1**: Use an LLM that automatically calls tools in English
+- Many modern LLMs can do this if properly instructed
+
+**Option 2**: Tool chain approach
+```csharp
+[KernelFunction]
+[Description("Translate text to English")]
+public async Task TranslateToEnglish(string text)
+{
+ // Translation logic
+}
+
+[KernelFunction]
+[Description("Search knowledge base (English only)")]
+public async Task SearchKnowledgeBase(string englishQuery)
+{
+ // Search logic
+}
+```
+
+The LLM will:
+1. Call `TranslateToEnglish("2024 geliri nedir?")`
+2. Get "What was 2024 revenue?"
+3. Call `SearchKnowledgeBase("What was 2024 revenue?")`
+4. Return results and respond in Turkish
+
+## Model Context Protocol (MCP): Beyond In-Process Tools
+
+Microsoft and Anthropic recently released official C# SDKs for the Model Context Protocol (MCP). This is a game-changer for tool reusability.
+
+
+
+### MCP vs. Semantic Kernel Plugins
+
+| Feature | SK Plugins | MCP Servers |
+|---------|-----------|-------------|
+| **Process** | In-process | Out-of-process (stdio/http) |
+| **Reusability** | Application-specific | Cross-application |
+| **Examples** | Used within your app | VS Code Copilot, Claude Desktop |
+
+### Creating an MCP Server
+
+```csharp
+using Microsoft.Extensions.Hosting;
+using ModelContextProtocol.Extensions.Hosting;
+
+var builder = Host.CreateEmptyApplicationBuilder(settings: null);
+
+builder.Services.AddMcpServer()
+.WithStdioServerTransport()
+.WithToolsFromAssembly();
+
+await builder.Build().RunAsync();
+```
+
+Define your tools:
+
+```csharp
+[McpServerToolType]
+public static class FileSystemTools
+{
+ [McpServerTool, Description("Read a file from the file system")]
+ public static async Task ReadFile(string path)
+ {
+ // ⚠️ SECURITY: Always validate paths!
+ if (!IsPathSafe(path))
+ throw new SecurityException("Invalid path");
+
+ return await File.ReadAllTextAsync(path);
+ }
+
+ private static bool IsPathSafe(string path)
+ {
+ // Implement path traversal prevention
+ var fullPath = Path.GetFullPath(path);
+ return fullPath.StartsWith(AllowedDirectory);
+ }
+}
+```
+
+Your MCP server can now be used by VS Code Copilot, Claude Desktop, or any other MCP client!
+
+## Chat History Management: Truncation + RAG Hybrid
+
+For long conversations, storing all history in the context window becomes impractical. Here's the pattern that works:
+
+
+
+### ❌ Lossy Approach
+```
+First 50 messages → Summarize with LLM → Single summary message
+```
+**Problem**: Detail loss (fidelity loss)
+
+### ✅ Hybrid Approach
+1. **Recent messages** (last 5-10): Keep in prompt for immediate context
+2. **Older messages**: Store in vector database as a tool
+
+```csharp
+[KernelFunction]
+[Description("Search conversation history for past discussions")]
+public async Task SearchChatHistory(
+ [Description("What to search for")] string query)
+{
+ var relevantMessages = await _vectorDb.SearchAsync(query);
+ return string.Join("\n", relevantMessages.Select(m =>
+ $"[{m.Timestamp}] {m.Role}: {m.Content}"));
+}
+```
+
+The LLM retrieves only relevant past context when needed, avoiding summary-induced information loss.
+
+## RAG vs. Fine-Tuning: Choose Wisely
+
+A common misconception is using fine-tuning for knowledge injection. Here's when to use each:
+
+| Purpose | RAG | Fine-Tuning |
+|---------|-----|-------------|
+| **Goal** | Memory (provide facts) | Behavior (teach style) |
+| **Updates** | Dynamic (add docs anytime) | Static (requires retraining) |
+| **Cost** | Low dev, higher inference | High dev, lower inference |
+| **Hallucination** | Reduces | Doesn't reduce |
+| **Use Case** | Company docs, FAQs | Brand voice, specific format |
+
+**Common mistake**: "Let's fine-tune on our company documents" ❌
+**Better approach**: Use RAG! ✅
+
+Fine-tuning is for teaching the model *how* to respond, not *what* to know.
+
+**Source**: [Oracle - RAG vs Fine-Tuning](https://www.oracle.com/artificial-intelligence/generative-ai/retrieval-augmented-generation-rag/rag-fine-tuning/)
+
+## Bonus: Why SVG is Superior for LLM-Generated Images
+
+When using LLMs to generate diagrams and visualizations, always request SVG format instead of PNG or JPG.
+
+### Why SVG?
+
+✅ **Text-based** → LLMs produce better results
+✅ **Lower cost** → Fewer tokens than base64-encoded images
+✅ **Editable** → Easy to modify after generation
+✅ **Scalable** → Perfect quality at any size
+✅ **Version control friendly** → Works great in Git
+
+### Example Prompt
+
+```
+Create an architecture diagram showing PostgreSQL with pgvector integration.
+Format: SVG, 800x400 pixels. Show: .NET Application → EF Core → PostgreSQL → Vector Search.
+Use arrows to connect stages. Color scheme: Blue tones.
+```
+
+
+
+All diagrams in this article were generated as SVG, resulting in excellent quality and lower token costs!
+
+> **Pro Tip**: If you don't need photographs or complex renders, always choose SVG.
+
+## Architecture Roadmap: Putting It All Together
+
+Here's the recommended stack for building production LLM applications with .NET:
+
+1. **Orchestration**: Microsoft.Extensions.AI + Semantic Kernel (when needed)
+2. **Vector Database**: PostgreSQL + Pgvector.EntityFrameworkCore
+3. **RAG Pattern**: Parent-Child chunks with 10-20% overlap
+4. **Tools**: MCP servers for reusability
+5. **Reasoning**: ReasoningEffortLevel instead of temperature
+6. **Prompting**: Critical rules at the end
+7. **Cost Optimization**: Make RAG a tool, not automatic
+
+## Key Takeaways
+
+Let me summarize the most important production tips:
+
+1. **Temperature is gone** → Use `ReasoningEffortLevel` with GPT-5
+2. **Rules at the end** → Combat "Lost in the Middle"
+3. **RAG as a tool** → Reduce costs significantly
+4. **Parent-Child pattern** → Search small, respond with large
+5. **Always use overlap** → 10-20% is the standard
+6. **pgvector for most cases** → Unless you have billions of vectors
+7. **MCP for reusability** → One codebase, works everywhere
+8. **SVG for diagrams** → Better results, lower cost
+9. **Hybrid chat history** → Recent in prompt, old in vector DB
+10. **RAG > Fine-tuning** → For knowledge, not behavior
+
+Happy coding! 🚀
\ No newline at end of file
diff --git a/docs/en/Community-Articles/2025-11-22-building-production-ready-llm-applications/summary.md b/docs/en/Community-Articles/2025-11-22-building-production-ready-llm-applications/summary.md
new file mode 100644
index 0000000000..fb1d41af5c
--- /dev/null
+++ b/docs/en/Community-Articles/2025-11-22-building-production-ready-llm-applications/summary.md
@@ -0,0 +1 @@
+Learn how to build production-ready LLM applications with .NET. This comprehensive guide covers GPT-5 API changes, advanced RAG architectures with parent-child patterns, PostgreSQL pgvector integration, smart tool usage strategies, multilingual query handling, Model Context Protocol (MCP) for cross-application tool reusability, and chat history management techniques for enterprise applications.
diff --git a/docs/en/Community-Articles/2025-11-30-NET-Conf-China-2025/POST.md b/docs/en/Community-Articles/2025-11-30-NET-Conf-China-2025/POST.md
new file mode 100644
index 0000000000..6f8dfb96a1
--- /dev/null
+++ b/docs/en/Community-Articles/2025-11-30-NET-Conf-China-2025/POST.md
@@ -0,0 +1,60 @@
+# .NET Conf China 2025: Changing the World, Changing Ourselves - See You Again in Shanghai
+
+
+
+.NET Conf China 2025 is an annual community event for developers, celebrating the release of .NET 10 (LTS) and the achievements of the past year in China. As an extension of .NET Conf 2025, this event brings together local tech communities, well-known companies, and open-source organizations. It has become the largest .NET online and offline conference in China, dedicated to spreading .NET technology in Chinese and fostering collaboration and exchange.
+
+## Event Highlights: Key Topics and Takeaways
+
+This year’s conference focused on three main themes: performance improvements, AI integration, and cross-platform development. Topics covered how to achieve performance gains while maintaining engineering quality, balancing between multi-platform consistency and native capabilities, and taking generative AI from “demo-level” to “production-ready.” On the community and ecosystem side, the event showcased the .NET Foundation’s and domestic and international companies’ progress in supporting architectures like ARM, LoongArch, and RISC-V. It also highlighted best practices in DevOps, observability, and engineering toolchains, creating a complete path from ideas to implementation.
+
+### Opening Keynote
+
+Scott Hanselman kicked off .NET Conf China 2025 with a video keynote, announcing that .NET 10 is now available on the official website. He framed the release around four pillars—AI, cloud-native, cross-platform, and performance—including integration with the Microsoft Agent Framework for building and orchestrating multi-agent systems in .NET/C#, industry-leading container and Kubernetes support with .NET Aspire simplifying local containerized development, a richer cross-platform desktop ecosystem (.NET MAUI, Avalonia, Uno Platform), and major performance gains such as Native AOT and single-file publishing for faster startup and easier distribution across platforms.
+
+He underscored China’s importance as .NET’s second-largest market, with roughly 13% of users, and noted that generative AI usage in China has doubled in 2025. The local community is seeing strong momentum around ML.NET, .NET Aspire, and the C# Dev Kit in VS Code. Reflecting on his Baby Smash game written 20 years ago, which now runs cross-platform on .NET 10, he called on developers to modernize: move existing Web, WinForms, and WPF apps to the cloud, improve performance, ship as a single executable, and weave in AI capabilities.
+
+On AI, he emphasized a human-centered stance: AI and agents should augment, not replace, developers. In the future, developers will orchestrate and govern agents, and human judgment will matter more than ever. He closed by thanking the open-source community for its many proposals and pull requests, stressing that .NET is an open-source platform built together by Microsoft and the community, and wishing everyone an inspiring conference and a joyful journey with .NET 10.
+
+
+
+### Roundtable Discussion
+
+The roundtable discussion, titled “Empowering with AI, Breaking Through Cross-Platform Barriers, and Ecosystem Innovation,” focused on practical implementation. It explored typical paths for large models and intelligent agents in enterprises, key considerations for choosing cross-platform UI frameworks, and the evolution of these frameworks. Panelists discussed questions like: How can AI capabilities be integrated into existing business processes instead of creating an “experimental” pipeline? How should cross-platform solutions be evaluated in terms of performance, ecosystem, and team skillsets? What are the unique opportunities for domestic ecosystems in the global tech landscape? And how can community collaboration help developers quickly adopt best practices? A shared consensus emerged: in the short term, focus on running scenarios; in the long term, return to engineering fundamentals. Both toolchains and methodologies are equally important.
+
+
+
+### In-Depth Sessions
+
+The afternoon featured four breakout sessions, covering a wide range of topics with deep dives into both foundational technologies and real-world project reviews:
+
+- **Frontend and Cross-Platform:** Focused on the progress of Avalonia, Blazor, and WebAssembly, as well as the integrated experience of .NET Aspire in multi-service applications. Speakers shared insights on reusing core logic between desktop and web, shortening cold start times with incremental compilation and resource trimming, and performance profiling and optimization in WASM scenarios.
+- **AI Agents and Enterprise Adoption:** Discussed multi-agent orchestration, the MCP plugin ecosystem, and enterprise data compliance. From common pitfalls of “demo-level” AI to the “five-step method” for moving from POC to production, the session covered use cases like knowledge retrieval, process automation, intelligent customer service, and developer assistants, emphasizing evaluation metrics, prompt engineering, and monitoring governance.
+- **.NET Practices and Engineering:** Focused on the latest capabilities and performance practices of EF Core, the boundaries of NativeAOT, automated testing strategies, and observability implementation. Discussions included database migration strategies, caching and concurrency control for hot paths, end-to-end tracing, and structured logging.
+- **Solutions and Case Studies:** From Clean Architecture/DDD to AI-powered business evolution, topics included application modernization, SaaS transformation, and edge-cloud collaboration in AIoT. Speakers broke down modular governance, team collaboration, and release strategies for complex systems, putting “delivering value continuously” at the center stage.
+
+
+
+## ABP Booth Highlights: Showcases, Conversations, and Fun
+
+The story of ABP began with a promise to create a better starting point. From the frustration of “copy-pasting boilerplate code,” we crafted a modular, opinionated framework. We chose open source and community collaboration. We founded Volosoft to turn our vision into reality with professional tools. Today, tens of thousands of developers explore the ABP framework, and thousands of teams rely on the ABP platform to deliver production-grade .NET applications faster and more securely.
+
+
+
+At .NET Conf China 2025, we brought our “developer platform built for developers” to every visitor. Our booth demonstrations started with “a production-ready skeleton from the start”: modular layered architecture, built-in authentication and authorization systems, multi-tenancy support, audit logging, and localization—all out of the box. On the frontend and backend, ABP offers diverse options like MVC, Blazor, and Angular, enabling teams to quickly implement solutions on familiar stacks while maintaining flexibility for future evolution. We also showcased how ABP integrates with containerization, CI/CD, and observability, emphasizing “engineering built into the framework, not reinvented by every team.”
+
+
+
+**Interaction and Prizes:** Sharing technology should also be warm and engaging. We hosted a QR code raffle at the booth, with prizes including ABP stickers, the book *Mastering ABP Framework*, and Bluetooth headphones. Multiple rounds of raffles and group photos made the interactions more memorable. Many developers shared their ABP experiences and plans for improvement right at the booth, and a few impromptu “code walkthroughs” naturally happened. The love and joy for technology were captured in every handshake and discussion.
+
+
+
+## Looking Ahead: Building the Ecosystem Together
+
+From an open-source journey to a complete development platform for the future, we’ve always believed that developers deserve a better starting point. Around performance, intelligence, and cross-platform capabilities, we will continue investing in engineering, ecosystem collaboration, and best practice sharing. We also welcome more partners to contribute through documentation and examples, share your experiences, and submit your ideas. Together, let’s make “useful infrastructure” more stable, efficient, and business-friendly.
+
+We look forward to exchanging ideas, sharing practices, and building the ecosystem together at the next gathering. Technology meets creativity, and the possibilities are endless. We’re on the road and waiting for you at the next event.
+
+See you next year at .NET Conf China 2026!
+
+
\ No newline at end of file
diff --git a/docs/en/Community-Articles/2025-11-30-NET-Conf-China-2025/images/1.png b/docs/en/Community-Articles/2025-11-30-NET-Conf-China-2025/images/1.png
new file mode 100644
index 0000000000..beaf49b86e
Binary files /dev/null and b/docs/en/Community-Articles/2025-11-30-NET-Conf-China-2025/images/1.png differ
diff --git a/docs/en/Community-Articles/2025-11-30-NET-Conf-China-2025/images/2.png b/docs/en/Community-Articles/2025-11-30-NET-Conf-China-2025/images/2.png
new file mode 100644
index 0000000000..a081bf99e3
Binary files /dev/null and b/docs/en/Community-Articles/2025-11-30-NET-Conf-China-2025/images/2.png differ
diff --git a/docs/en/Community-Articles/2025-11-30-NET-Conf-China-2025/images/21.png b/docs/en/Community-Articles/2025-11-30-NET-Conf-China-2025/images/21.png
new file mode 100644
index 0000000000..345452360a
Binary files /dev/null and b/docs/en/Community-Articles/2025-11-30-NET-Conf-China-2025/images/21.png differ
diff --git a/docs/en/Community-Articles/2025-11-30-NET-Conf-China-2025/images/3.png b/docs/en/Community-Articles/2025-11-30-NET-Conf-China-2025/images/3.png
new file mode 100644
index 0000000000..b69f36ef66
Binary files /dev/null and b/docs/en/Community-Articles/2025-11-30-NET-Conf-China-2025/images/3.png differ
diff --git a/docs/en/Community-Articles/2025-11-30-NET-Conf-China-2025/images/4.png b/docs/en/Community-Articles/2025-11-30-NET-Conf-China-2025/images/4.png
new file mode 100644
index 0000000000..a3a2ece3e9
Binary files /dev/null and b/docs/en/Community-Articles/2025-11-30-NET-Conf-China-2025/images/4.png differ
diff --git a/docs/en/Community-Articles/2025-11-30-NET-Conf-China-2025/images/41.png b/docs/en/Community-Articles/2025-11-30-NET-Conf-China-2025/images/41.png
new file mode 100644
index 0000000000..19143279aa
Binary files /dev/null and b/docs/en/Community-Articles/2025-11-30-NET-Conf-China-2025/images/41.png differ
diff --git a/docs/en/Community-Articles/2025-11-30-NET-Conf-China-2025/images/42.png b/docs/en/Community-Articles/2025-11-30-NET-Conf-China-2025/images/42.png
new file mode 100644
index 0000000000..730969eb8e
Binary files /dev/null and b/docs/en/Community-Articles/2025-11-30-NET-Conf-China-2025/images/42.png differ
diff --git a/docs/en/Community-Articles/2025-11-30-NET-Conf-China-2025/images/5.png b/docs/en/Community-Articles/2025-11-30-NET-Conf-China-2025/images/5.png
new file mode 100644
index 0000000000..f1a2a437a0
Binary files /dev/null and b/docs/en/Community-Articles/2025-11-30-NET-Conf-China-2025/images/5.png differ
diff --git a/docs/en/Community-Articles/2025-11-30-NET-Conf-China-2025/images/cover.png b/docs/en/Community-Articles/2025-11-30-NET-Conf-China-2025/images/cover.png
new file mode 100644
index 0000000000..f0eb6cea5f
Binary files /dev/null and b/docs/en/Community-Articles/2025-11-30-NET-Conf-China-2025/images/cover.png differ
diff --git a/docs/en/Community-Articles/2025-12-06-Implement-Automatic-Method-Level-Caching-in-ABP-Framework/cover.png b/docs/en/Community-Articles/2025-12-06-Implement-Automatic-Method-Level-Caching-in-ABP-Framework/cover.png
new file mode 100644
index 0000000000..9eee8f6d07
Binary files /dev/null and b/docs/en/Community-Articles/2025-12-06-Implement-Automatic-Method-Level-Caching-in-ABP-Framework/cover.png differ
diff --git a/docs/en/Community-Articles/2025-12-06-Implement-Automatic-Method-Level-Caching-in-ABP-Framework/images/architecture-diagram.svg b/docs/en/Community-Articles/2025-12-06-Implement-Automatic-Method-Level-Caching-in-ABP-Framework/images/architecture-diagram.svg
new file mode 100644
index 0000000000..d0c5fd900a
--- /dev/null
+++ b/docs/en/Community-Articles/2025-12-06-Implement-Automatic-Method-Level-Caching-in-ABP-Framework/images/architecture-diagram.svg
@@ -0,0 +1,145 @@
+
\ No newline at end of file
diff --git a/docs/en/Community-Articles/2025-12-06-Implement-Automatic-Method-Level-Caching-in-ABP-Framework/images/automatic-caching-flow.svg b/docs/en/Community-Articles/2025-12-06-Implement-Automatic-Method-Level-Caching-in-ABP-Framework/images/automatic-caching-flow.svg
new file mode 100644
index 0000000000..9ea54b1f46
--- /dev/null
+++ b/docs/en/Community-Articles/2025-12-06-Implement-Automatic-Method-Level-Caching-in-ABP-Framework/images/automatic-caching-flow.svg
@@ -0,0 +1,82 @@
+
\ No newline at end of file
diff --git a/docs/en/Community-Articles/2025-12-06-Implement-Automatic-Method-Level-Caching-in-ABP-Framework/images/cache-invalidation-flow.svg b/docs/en/Community-Articles/2025-12-06-Implement-Automatic-Method-Level-Caching-in-ABP-Framework/images/cache-invalidation-flow.svg
new file mode 100644
index 0000000000..d0281902d8
--- /dev/null
+++ b/docs/en/Community-Articles/2025-12-06-Implement-Automatic-Method-Level-Caching-in-ABP-Framework/images/cache-invalidation-flow.svg
@@ -0,0 +1,141 @@
+
\ No newline at end of file
diff --git a/docs/en/Community-Articles/2025-12-06-Implement-Automatic-Method-Level-Caching-in-ABP-Framework/images/cache-scoping-diagram.svg b/docs/en/Community-Articles/2025-12-06-Implement-Automatic-Method-Level-Caching-in-ABP-Framework/images/cache-scoping-diagram.svg
new file mode 100644
index 0000000000..848d9d0c51
--- /dev/null
+++ b/docs/en/Community-Articles/2025-12-06-Implement-Automatic-Method-Level-Caching-in-ABP-Framework/images/cache-scoping-diagram.svg
@@ -0,0 +1,135 @@
+
\ No newline at end of file
diff --git a/docs/en/Community-Articles/2025-12-06-Implement-Automatic-Method-Level-Caching-in-ABP-Framework/post.md b/docs/en/Community-Articles/2025-12-06-Implement-Automatic-Method-Level-Caching-in-ABP-Framework/post.md
new file mode 100644
index 0000000000..50a4aba33e
--- /dev/null
+++ b/docs/en/Community-Articles/2025-12-06-Implement-Automatic-Method-Level-Caching-in-ABP-Framework/post.md
@@ -0,0 +1,797 @@
+# Implement Automatic Method-Level Caching in ABP Framework
+
+Caching is one of the most effective ways to improve application performance, but implementing it manually for every method can be tedious and error-prone. What if you could cache method results automatically with just an attribute? In this article, we'll explore how to build an automatic method-level caching system in ABP Framework that handles cache invalidation, supports multiple scopes, and integrates seamlessly with your existing application.
+
+By the end of this guide, you'll understand how to implement attribute-based caching that automatically invalidates when entities change, supports user-specific and global caching scopes, and provides built-in metrics for monitoring cache performance.
+
+> 💡 **Complete Implementation Available**: This article is based on a working demo project. You can find the complete implementation in the [AbpAutoCacheDemo repository](https://github.com/salihozkara/AbpAutoCacheDemo), with the core AutoCache library implementation available in [this commit](https://github.com/salihozkara/AbpAutoCacheDemo/commit/946df1fc07de6eddd26eb14013a09968cd59329b).
+
+## What is Automatic Method-Level Caching?
+
+Automatic method-level caching is a technique that intercepts method calls and caches their results without requiring manual cache management code. Instead of writing cache logic in every method, you simply decorate methods with attributes that define caching behavior.
+
+
+
+The key benefits include:
+
+- **Reduced Boilerplate:** No repetitive cache management code in your business logic
+- **Consistent Caching Strategy:** Centralized cache configuration and behavior
+- **Smart Invalidation:** Automatic cache clearing when related entities change
+- **Multiple Scopes:** Support for global, user-specific, and entity-specific caching
+- **Built-in Monitoring:** Track cache hits, misses, and performance metrics
+
+## Architecture Overview
+
+The automatic caching system consists of several key components working together:
+
+
+
+**Core Components:**
+
+1. **CacheAttribute:** The attribute you apply to methods to enable automatic caching
+2. **AutoCacheInterceptor:** Intercepts method calls and handles cache operations
+3. **AutoCacheManager:** Manages cache storage, retrieval, and key generation
+4. **IAutoCacheKeyManager:** Handles cache key mapping and invalidation
+5. **AutoCacheInvalidationHandler:** Listens to entity changes and clears related caches
+
+This architecture leverages ABP's dynamic proxy system and event bus to provide seamless caching without modifying your business logic.
+
+## Prerequisites
+
+Before implementing automatic caching, ensure you have:
+
+- ABP Framework 10.0 or later
+## Implementation
+
+> 📦 **Repository Structure**: The complete implementation is available in the [AbpAutoCacheDemo repository](https://github.com/salihozkara/AbpAutoCacheDemo). The AutoCache library is located in the `src/AutoCache` folder, making it easy to extract and reuse in your own projects.
+
+### Step - 1: Create the AutoCache Module
+
+First, let's create a separate module for our caching infrastructure. This makes it reusable across projects.
+
+### Step - 1: Create the AutoCache Module
+
+First, let's create a separate module for our caching infrastructure. This makes it reusable across projects.
+
+Create `AutoCache.csproj`:
+
+```xml
+
+
+ net10.0
+ enable
+
+
+
+
+
+
+
+
+```
+
+Create the module class `AutoCacheModule.cs`:
+
+```csharp
+using Microsoft.Extensions.DependencyInjection;
+using Volo.Abp.Caching.StackExchangeRedis;
+using Volo.Abp.Domain;
+using Volo.Abp.Modularity;
+
+namespace AutoCache;
+
+[DependsOn(typeof(AbpDddDomainModule), typeof(AbpCachingStackExchangeRedisModule))]
+public class AutoCacheModule : AbpModule
+{
+ public override void PreConfigureServices(ServiceConfigurationContext context)
+ {
+ context.Services.OnRegistered(AutoCacheRegister.RegisterInterceptorIfNeeded); // 👈 Register interceptor
+ }
+}
+```
+
+This module automatically registers the cache interceptor for any class that uses the `CacheAttribute`.
+
+### Step - 2: Define the Cache Attribute
+
+The `CacheAttribute` is the core of our automatic caching system. It specifies which entities affect the cache and what scope to use.
+
+Create `CacheAttribute.cs`:
+
+```csharp
+using System;
+using Volo.Abp.Domain.Entities;
+
+namespace AutoCache;
+
+[AttributeUsage(AttributeTargets.Method)]
+public class CacheAttribute : Attribute
+{
+ ///
+ /// Entity types that affect this cache. When these entities change, the cache will be invalidated.
+ ///
+ public Type[] InvalidateOnEntities { get; set; }
+
+ ///
+ /// Scope of the cache (Global, CurrentUser, AuthenticatedUser, or Entity)
+ ///
+ public AutoCacheScope Scope { get; set; } = AutoCacheScope.Global;
+
+ ///
+ /// Absolute expiration time relative to now in milliseconds (0 = use default, -1 = disabled)
+ ///
+ public long AbsoluteExpirationRelativeToNow { get; set; }
+
+ ///
+ /// Sliding expiration time in milliseconds (0 = use default, -1 = disabled)
+ ///
+ public long SlidingExpiration { get; set; }
+
+ public bool ConsiderUow { get; set; }
+
+ public string AdditionalCacheKey { get; set; }
+
+ public CacheAttribute(params Type[] invalidateOnEntities) // 👈 Specify entities that trigger cache invalidation
+ {
+ foreach (var entityType in invalidateOnEntities)
+ {
+ ArgumentNullException.ThrowIfNull(entityType);
+ if (!typeof(IEntity).IsAssignableFrom(entityType))
+ {
+ throw new ArgumentException($"Type {entityType.FullName} must implement IEntity interface.");
+ }
+ }
+ InvalidateOnEntities = invalidateOnEntities;
+ }
+}
+```
+
+**Key Properties:**
+
+- **InvalidateOnEntities:** Array of entity types that, when modified, will clear this cache
+- **Scope:** Determines cache visibility (Global, CurrentUser, AuthenticatedUser, Entity)
+- **AbsoluteExpirationRelativeToNow / SlidingExpiration:** Control cache lifetime
+
+### Step - 3: Define Cache Scopes
+
+Cache scopes determine how cache entries are partitioned. Create `AutoCacheScope.cs`:
+
+```csharp
+using System;
+
+namespace AutoCache;
+
+[Flags]
+public enum AutoCacheScope
+{
+ ///
+ /// Cache is shared globally across all users
+ ///
+ Global,
+
+ ///
+ /// Cache is scoped to the current user (based on user ID)
+ ///
+ CurrentUser,
+
+ ///
+ /// Cache is scoped to authenticated vs unauthenticated users
+ ///
+ AuthenticatedUser,
+
+ ///
+ /// Cache is scoped to the primary key of the entity involved
+ ///
+ Entity
+}
+```
+
+
+
+**When to Use Each Scope:**
+
+- **Global:** For data that's the same for all users (e.g., configuration, public lists)
+- **CurrentUser:** For user-specific data (e.g., user profile, user's orders)
+- **AuthenticatedUser:** For data that differs between authenticated and anonymous users
+- **Entity:** For data tied to a specific entity instance (e.g., book details by ID)
+
+### Step - 4: Implement the Cache Interceptor
+
+The interceptor is the heart of automatic caching. It intercepts method calls, checks the cache, and stores results. Create `AutoCacheInterceptor.cs`:
+
+```csharp
+using System;
+using System.Collections.Concurrent;
+using System.Linq;
+using System.Reflection;
+using System.Threading.Tasks;
+using Microsoft.Extensions.Caching.Distributed;
+using Microsoft.Extensions.Logging;
+using Microsoft.Extensions.Options;
+using Volo.Abp.DependencyInjection;
+using Volo.Abp.DynamicProxy;
+
+namespace AutoCache;
+
+public class AutoCacheInterceptor : AbpInterceptor, ITransientDependency
+{
+ private readonly ILogger _logger;
+ private readonly AutoCacheOptions _options;
+ private static readonly MethodInfo GetOrAddCacheAsyncMethod;
+ private readonly AutoCacheManager _autoCacheManager;
+ private static readonly ConcurrentDictionary MethodCache = new();
+
+ static AutoCacheInterceptor()
+ {
+ GetOrAddCacheAsyncMethod = typeof(AutoCacheInterceptor).GetMethod(
+ nameof(GetOrAddCacheAsync),
+ BindingFlags.NonPublic | BindingFlags.Instance
+ )!;
+ }
+
+ public AutoCacheInterceptor(
+ ILogger logger,
+ IOptions options,
+ AutoCacheManager autoCacheManager)
+ {
+ _logger = logger;
+ _autoCacheManager = autoCacheManager;
+ _options = options.Value;
+ }
+
+ public override async Task InterceptAsync(IAbpMethodInvocation invocation)
+ {
+ // Check if caching is enabled and method has [Cache] attribute
+ if(!_options.Enabled ||
+ invocation.Method.GetCustomAttributes(typeof(CacheAttribute), true).FirstOrDefault()
+ is not CacheAttribute attribute)
+ {
+ await invocation.ProceedAsync(); // 👈 No caching, proceed normally
+ return;
+ }
+
+ var proceeded = false;
+
+ try
+ {
+ // Create generic method based on return type
+ var genericMethod = MethodCache.GetOrAdd(invocation.Method.ReturnType, t =>
+ {
+ var isGenericTask = t.IsGenericType && t.GetGenericTypeDefinition() == typeof(Task<>);
+ var resultType = isGenericTask ? t.GetGenericArguments()[0] : t;
+ return GetOrAddCacheAsyncMethod.MakeGenericMethod(resultType);
+ });
+
+ // Execute cache logic
+ (var result, proceeded) = await (Task<(object, bool)>)genericMethod.Invoke(this, [invocation, attribute])!;
+ invocation.ReturnValue = result; // 👈 Set cached or fresh result
+ }
+ catch (Exception e)
+ {
+ _logger.LogError(e, "Error occurred while caching method {MethodName}", invocation.Method.Name);
+
+ if(e is AutoCacheExceptionWrapper exceptionWrapper)
+ {
+ if (_options.ThrowOnError)
+ {
+ throw exceptionWrapper.OriginalException;
+ }
+
+ _logger.LogWarning(
+ "Cache operation failed, falling back to method execution for {MethodName}",
+ invocation.Method.Name
+ );
+ }
+
+ if (!proceeded && invocation.ReturnValue == null)
+ {
+ await invocation.ProceedAsync(); // 👈 Fallback to actual method execution
+ }
+ }
+ }
+
+ private async Task<(object?, bool)> GetOrAddCacheAsync(
+ IAbpMethodInvocation invocation,
+ CacheAttribute attribute)
+ {
+ var proceeded = false;
+ var result = await _autoCacheManager.GetOrAddAsync(
+ invocation.TargetObject,
+ Factory,
+ invocation.Arguments,
+ () => new DistributedCacheEntryOptions
+ {
+ AbsoluteExpirationRelativeToNow = GetExpiration(
+ attribute.AbsoluteExpirationRelativeToNow,
+ _options.DefaultAbsoluteExpirationRelativeToNow),
+ SlidingExpiration = GetExpiration(
+ attribute.SlidingExpiration,
+ _options.DefaultSlidingExpiration)
+ },
+ attribute.InvalidateOnEntities,
+ attribute.Scope,
+ attribute.ConsiderUow,
+ attribute.AdditionalCacheKey,
+ invocation.Method.Name);
+
+ return (result, proceeded);
+
+ async Task Factory()
+ {
+ await invocation.ProceedAsync(); // 👈 Execute actual method on cache miss
+ proceeded = true;
+ return (TResult)invocation.ReturnValue;
+ }
+ }
+
+ private static TimeSpan? GetExpiration(long milliseconds, long defaultValue)
+ {
+ return milliseconds switch
+ {
+ 0 => defaultValue > 0 ? TimeSpan.FromMilliseconds(defaultValue) : null,
+ < 0 => null,
+ _ => TimeSpan.FromMilliseconds(milliseconds)
+ };
+ }
+}
+```
+
+The interceptor intelligently determines whether to serve cached data or execute the actual method.
+
+### Step - 5: Implement the Cache Manager
+
+The `AutoCacheManager` handles the actual cache operations. Create a simplified version:
+
+```csharp
+using System;
+using System.Runtime.CompilerServices;
+using System.Threading.Tasks;
+using Microsoft.Extensions.Caching.Distributed;
+using Microsoft.Extensions.Logging;
+using Volo.Abp.DependencyInjection;
+using Volo.Abp.DynamicProxy;
+using Volo.Abp.Users;
+
+namespace AutoCache;
+
+public class AutoCacheManager : IScopedDependency
+{
+ private readonly IAutoCacheKeyManager _autoCacheKeyManager;
+ private readonly ICurrentUser _currentUser;
+ private readonly ILogger _logger;
+ private readonly IAutoCacheMetrics _metrics;
+ private readonly AutoCacheOptions _options;
+
+ public AutoCacheManager(
+ IAutoCacheKeyManager autoCacheKeyManager,
+ ICurrentUser currentUser,
+ ILogger logger,
+ IAutoCacheMetrics metrics,
+ IOptions options)
+ {
+ _autoCacheKeyManager = autoCacheKeyManager;
+ _currentUser = currentUser;
+ _logger = logger;
+ _metrics = metrics;
+ _options = options.Value;
+ }
+
+ public async Task GetOrAddAsync(
+ object? caller,
+ Func> func,
+ object?[]? parameters = null,
+ Func? optionsFactory = null,
+ Type[]? invalidateOnEntities = null,
+ AutoCacheScope scope = AutoCacheScope.Global,
+ bool considerUow = false,
+ string? additionalCacheKey = null,
+ [CallerMemberName] string methodName = "")
+ {
+ if (!_options.Enabled)
+ {
+ return await func(); // 👈 Caching disabled, execute directly
+ }
+
+ var callerType = caller != null ? ProxyHelper.GetUnProxiedType(caller) : GetType();
+ parameters ??= [];
+
+ // Generate unique cache key based on method, parameters, and scope
+ var cacheKey = GenerateCacheKey(
+ callerType.Name,
+ additionalCacheKey,
+ methodName,
+ parameters,
+ scope);
+
+ var (cachedResult, exception, wasHit) = await GetOrAddCacheAsync(
+ cacheKey,
+ func,
+ optionsFactory,
+ considerUow
+ );
+
+ // Record metrics
+ if (wasHit)
+ {
+ _metrics.RecordHit(cacheKey);
+ }
+ else
+ {
+ _metrics.RecordMiss(cacheKey);
+ }
+
+ if (exception != null)
+ {
+ _metrics.RecordError(cacheKey, exception);
+
+ if (_options.ThrowOnError)
+ {
+ throw exception;
+ }
+ }
+
+ return cachedResult;
+ }
+
+ private string GenerateCacheKey(
+ string callerTypeName,
+ string? additionalCacheKey,
+ string methodName,
+ object?[] parameters,
+ AutoCacheScope scope)
+ {
+ var keyBuilder = new StringBuilder();
+ keyBuilder.Append($"{callerTypeName}:{methodName}");
+
+ // Add parameters to key
+ foreach (var param in parameters)
+ {
+ keyBuilder.Append($":{param}");
+ }
+
+ // Add scope-specific segments
+ if (scope.HasFlag(AutoCacheScope.CurrentUser) && _currentUser.Id.HasValue)
+ {
+ keyBuilder.Append($":user:{_currentUser.Id}"); // 👈 User-specific cache key
+ }
+
+ if (scope.HasFlag(AutoCacheScope.AuthenticatedUser))
+ {
+ keyBuilder.Append($":auth:{_currentUser.IsAuthenticated}");
+ }
+
+ if (!string.IsNullOrEmpty(additionalCacheKey))
+ {
+ keyBuilder.Append($":{additionalCacheKey}");
+ }
+
+ return keyBuilder.ToString();
+ }
+
+ // Additional methods for cache retrieval and storage...
+}
+```
+
+The manager generates unique cache keys based on method signatures, parameters, and scope settings.
+
+### Step - 6: Implement Cache Invalidation
+
+When entities change, related caches must be cleared. Create `AutoCacheInvalidationHandler.cs`:
+
+```csharp
+using System;
+using System.Threading.Tasks;
+using Microsoft.Extensions.Logging;
+using Volo.Abp.Domain.Entities;
+using Volo.Abp.Domain.Entities.Events;
+using Volo.Abp.EventBus;
+using Volo.Abp.Uow;
+
+namespace AutoCache;
+
+public class AutoCacheInvalidationHandler :
+ ILocalEventHandler>
+ where TEntity : class, IEntity
+{
+ private readonly IAutoCacheKeyManager _autoCacheKeyManager;
+ private readonly ILogger> _logger;
+ private readonly IUnitOfWorkManager _unitOfWorkManager;
+
+ public AutoCacheInvalidationHandler(
+ IAutoCacheKeyManager autoCacheKeyManager,
+ ILogger> logger,
+ IUnitOfWorkManager unitOfWorkManager)
+ {
+ _autoCacheKeyManager = autoCacheKeyManager;
+ _logger = logger;
+ _unitOfWorkManager = unitOfWorkManager;
+ }
+
+ public async Task HandleEventAsync(EntityChangedEventData eventData)
+ {
+ try
+ {
+ var entityType = typeof(TEntity);
+ var context = new RemoveCacheKeyContext
+ {
+ Keys = eventData.Entity.GetKeys()!
+ };
+
+ // Clear cache after unit of work completes
+ if(_unitOfWorkManager.Current != null)
+ {
+ _unitOfWorkManager.Current.OnCompleted(async () =>
+ {
+ await _autoCacheKeyManager.RemoveCacheAndCacheKeys(entityType, context); // 👈 Invalidate cache
+ });
+ }
+ else
+ {
+ await _autoCacheKeyManager.RemoveCacheAndCacheKeys(entityType, context);
+ }
+ }
+ catch (Exception e)
+ {
+ _logger.LogError(
+ e,
+ "Error occurred while clearing cache for entity type {EntityType}",
+ typeof(TEntity).FullName
+ );
+ }
+ }
+}
+```
+
+
+
+This handler listens to entity change events and automatically clears related caches. The invalidation happens after the unit of work completes to ensure data consistency.
+
+### Step - 7: Configure AutoCache in Your Application
+
+Add the `AutoCacheModule` to your application module dependencies:
+
+```csharp
+[DependsOn(
+ typeof(AutoCacheModule), // 👈 Add AutoCache module
+ typeof(AbpCachingStackExchangeRedisModule),
+ // ... other modules
+)]
+public class YourApplicationModule : AbpModule
+{
+ public override void ConfigureServices(ServiceConfigurationContext context)
+ {
+ Configure(options =>
+ {
+ options.Enabled = true; // 👈 Enable caching
+ options.DefaultAbsoluteExpirationRelativeToNow = 3600000; // 1 hour
+ options.DefaultSlidingExpiration = 600000; // 10 minutes
+ options.ThrowOnError = false; // Fallback to method execution on cache errors
+ });
+
+ // Configure Redis (if using distributed cache)
+ Configure(options =>
+ {
+ options.KeyPrefix = "YourApp:";
+ });
+ }
+}
+```
+
+### Step - 8: Use Automatic Caching in Application Services
+
+Now comes the easy part - using automatic caching! Simply add the `[Cache]` attribute to your methods:
+
+```csharp
+using AutoCache;
+
+[Authorize(AutoCacheDemoPermissions.Books.Default)]
+public class BookAppService : ApplicationService, IBookAppService
+{
+ private readonly IRepository _repository;
+ private readonly AutoCacheManager _autoCacheManager;
+
+ public BookAppService(IRepository repository, AutoCacheManager autoCacheManager)
+ {
+ _repository = repository;
+ _autoCacheManager = autoCacheManager;
+ }
+
+ // Cache this method, invalidate when Book entity changes
+ [Cache(typeof(Book), Scope = AutoCacheScope.Global)]
+ public virtual async Task GetAsync(Guid id)
+ {
+ // You can also use AutoCacheManager directly for nested caching
+ var book = await _autoCacheManager.GetOrAddAsync(
+ this,
+ async () => await _repository.GetAsync(id),
+ [id], // 👈 Method parameters
+ invalidateOnEntities: [typeof(Book)],
+ scope: AutoCacheScope.Entity);
+
+ return ObjectMapper.Map(book!);
+ }
+
+ // Cache book list, invalidate when any Book changes
+ [Cache(typeof(Book))]
+ public virtual async Task> GetListAsync(PagedAndSortedResultRequestDto input)
+ {
+ var queryable = await _repository.GetQueryableAsync();
+ var query = queryable
+ .OrderBy(input.Sorting.IsNullOrWhiteSpace() ? "Name" : input.Sorting)
+ .Skip(input.SkipCount)
+ .Take(input.MaxResultCount);
+
+ var books = await AsyncExecuter.ToListAsync(query);
+ var totalCount = await AsyncExecuter.CountAsync(queryable);
+
+ return new PagedResultDto(
+ totalCount,
+ ObjectMapper.Map, List>(books)
+ );
+ }
+
+ // No caching on write operations
+ [Authorize(AutoCacheDemoPermissions.Books.Create)]
+ public async Task CreateAsync(CreateUpdateBookDto input)
+ {
+ var book = ObjectMapper.Map(input);
+ await _repository.InsertAsync(book); // 👈 This will trigger cache invalidation
+ return ObjectMapper.Map(book);
+ }
+}
+```
+
+**What Happens Here:**
+
+1. When `GetAsync` is called, the interceptor checks the cache
+2. On cache miss, the actual method executes and the result is cached
+3. When `CreateAsync` inserts a `Book`, the invalidation handler clears all caches related to `Book`
+4. Next call to `GetAsync` will fetch fresh data
+
+## Advanced Features
+
+### User-Specific Caching
+
+For user-specific data, use `AutoCacheScope.CurrentUser`:
+
+```csharp
+[Cache(typeof(Order), Scope = AutoCacheScope.CurrentUser)]
+public virtual async Task> GetMyOrdersAsync()
+{
+ var orders = await _orderRepository.GetListAsync(x => x.UserId == CurrentUser.Id);
+ return ObjectMapper.Map, List>(orders);
+}
+```
+
+Each user gets their own cache entry, automatically invalidated when their orders change.
+
+### Custom Cache Keys
+
+For fine-grained control, add custom cache key segments:
+
+```csharp
+[Cache(
+ typeof(Product),
+ Scope = AutoCacheScope.Global,
+ AdditionalCacheKey = "featured"
+)]
+public virtual async Task> GetFeaturedProductsAsync()
+{
+ // Only featured products are cached separately
+ return await GetProductsByCategoryAsync("Featured");
+}
+```
+
+### Performance Metrics
+
+Monitor cache performance using `IAutoCacheMetrics`:
+
+```csharp
+public class CacheMonitoringService : ITransientDependency
+{
+ private readonly IAutoCacheMetrics _metrics;
+
+ public CacheMonitoringService(IAutoCacheMetrics metrics)
+ {
+ _metrics = metrics;
+ }
+
+ public AutoCacheStatistics GetStatistics()
+ {
+ return _metrics.GetStatistics(); // 👈 Get hit rate, miss count, error count
+ }
+}
+```
+
+## Testing the Application
+
+### 1. Run the Application
+
+```bash
+abp new BookStore -u mvc -d ef
+cd BookStore
+dotnet run --project src/BookStore.Web
+```
+
+### 2. Test Cache Behavior
+
+Create a simple test to verify caching:
+
+```csharp
+[Fact]
+public async Task Should_Cache_Book_Results()
+{
+ // First call - cache miss
+ var book1 = await _bookAppService.GetAsync(testBookId);
+
+ // Second call - cache hit (should be faster)
+ var book2 = await _bookAppService.GetAsync(testBookId);
+
+ book1.Name.ShouldBe(book2.Name);
+}
+
+[Fact]
+public async Task Should_Invalidate_Cache_On_Update()
+{
+ // Cache the book
+ var book1 = await _bookAppService.GetAsync(testBookId);
+
+ // Update the book
+ await _bookAppService.UpdateAsync(testBookId, new CreateUpdateBookDto
+ {
+ Name = "Updated Name"
+ });
+
+ // Fetch again - should get updated data (cache was invalidated)
+ var book2 = await _bookAppService.GetAsync(testBookId);
+
+ book2.Name.ShouldBe("Updated Name");
+}
+```
+
+### 3. Monitor Cache Performance
+
+Check your application logs for cache metrics:
+
+```
+[INF] Cache Hit: BookAppService:GetAsync:book-id-123 (Response Time: 5ms)
+[INF] Cache Miss: BookAppService:GetListAsync (Response Time: 156ms)
+[INF] Cache Invalidation: Book entity changed, cleared 3 cache entries
+```
+
+## Key Takeaways
+
+✅ **Automatic caching reduces boilerplate code** - Just add `[Cache]` attribute to methods instead of manual cache management
+
+✅ **Smart invalidation keeps data fresh** - Entity changes automatically clear related caches without manual intervention
+
+✅ **Multiple scoping options** - Support for global, user-specific, authenticated, and entity-level caching strategies
+
+✅ **Built-in fallback handling** - Gracefully falls back to method execution if caching fails
+
+✅ **Performance monitoring** - Track cache hits, misses, and errors for optimization
+
+## Conclusion
+
+Automatic method-level caching dramatically simplifies performance optimization in ABP Framework applications. By using attributes and interceptors, you can add sophisticated caching behavior without cluttering your business logic with cache management code.
+
+The system we've built provides intelligent cache invalidation, multiple scoping strategies, and built-in monitoring - all while maintaining clean, readable code. Whether you're building a small application or an enterprise system, this approach scales elegantly and integrates seamlessly with ABP's architecture.
+
+Ready to implement this in your project? The complete working implementation is available in the [AbpAutoCacheDemo repository](https://github.com/salihozkara/AbpAutoCacheDemo). You can clone the repository, explore the code, and even extract the `src/AutoCache` folder to use it as a standalone library in your own ABP applications. The [main implementation commit](https://github.com/salihozkara/AbpAutoCacheDemo/commit/946df1fc07de6eddd26eb14013a09968cd59329b) shows all the components working together, including interceptor registration, cache key management, and automatic invalidation handlers.r you're building a small application or an enterprise system, this approach scales elegantly and integrates seamlessly with ABP's architecture.
+
+Ready to implement this in your project? Check out the complete working example in the repository linked below, and start improving your application's performance today!
+
+### See Also
+
+- [ABP Caching Documentation](https://abp.io/docs/latest/framework/fundamentals/caching)
+- [Interceptors in ABP](https://abp.io/docs/latest/framework/infrastructure/interceptors)
+- [Event Bus Documentation](https://abp.io/docs/latest/framework/infrastructure/event-bus)
+- [Sample Project on GitHub](https://github.com/salihozkara/AbpAutoCacheDemo)
+
+---
+
+## References
+
+- [ABP Framework Documentation](https://docs.abp.io)
+- [Redis Distributed Caching](https://redis.io/docs/)
+- [Aspect-Oriented Programming Patterns](https://en.wikipedia.org/wiki/Aspect-oriented_programming)
diff --git a/docs/en/Community-Articles/2025-12-06-Implement-Automatic-Method-Level-Caching-in-ABP-Framework/summary.md b/docs/en/Community-Articles/2025-12-06-Implement-Automatic-Method-Level-Caching-in-ABP-Framework/summary.md
new file mode 100644
index 0000000000..a27494cd8a
--- /dev/null
+++ b/docs/en/Community-Articles/2025-12-06-Implement-Automatic-Method-Level-Caching-in-ABP-Framework/summary.md
@@ -0,0 +1 @@
+Learn how to implement automatic method-level caching in ABP Framework using attributes and interceptors. This comprehensive guide covers building a reusable cache infrastructure with attribute-based caching, intelligent cache invalidation when entities change, support for multiple cache scopes (Global, CurrentUser, AuthenticatedUser, and Entity), seamless integration with ABP's dynamic proxy system and event bus, and built-in performance metrics for monitoring cache effectiveness in production applications.
diff --git a/docs/en/aspect-oriented-programming.md b/docs/en/aspect-oriented-programming.md
deleted file mode 100644
index c578f1e89c..0000000000
--- a/docs/en/aspect-oriented-programming.md
+++ /dev/null
@@ -1,3 +0,0 @@
-# Dynamic Proxying / Interceptors
-
-This document is planned to be written later.
\ No newline at end of file
diff --git a/docs/en/cli/index.md b/docs/en/cli/index.md
index 99a79aabb9..3a3d0c2304 100644
--- a/docs/en/cli/index.md
+++ b/docs/en/cli/index.md
@@ -7,11 +7,7 @@
# ABP CLI
-ABP CLI (Command Line Interface) is a command line tool to perform some common operations for ABP based solutions or ABP Studio features.
-
-> With **v8.2+**, the old/legacy ABP CLI has been replaced with a new CLI system to align with the new templating system and [ABP Studio](../studio/index.md). The new ABP CLI commands are explained in this documentation. However, if you want to learn more about the differences between the old and new CLIs, want to learn the reason for the change, or need guidance to use the old ABP CLI, please refer to the [Old vs New CLI](differences-between-old-and-new-cli.md) documentation.
->
-> You may need to remove the Old CLI before installing the New CLI, by running the following command: `dotnet tool uninstall -g Volo.Abp.Cli`
+ABP CLI (Command Line Interface) is a command line tool to perform some common operations for ABP based solutions or [ABP Studio](../studio/index.md) features.
## Installation
@@ -29,16 +25,16 @@ dotnet tool update -g Volo.Abp.Studio.Cli
## Global Options
-While each command may have a set of options, there are some global options that can be used with any command;
+While each command may have a set of options, there are some global options that can be used with any command:
-* `--skip-cli-version-check` or `-scvc`: Skips to check the latest version of the ABP CLI. If you don't specify, it will check the latest version and shows a warning message if there is a newer version of the ABP CLI.
-- `--skip-extension-version-check` or `-sevc`: Skips to check the latest version of the ABP CLI extensions. If you don't specify, it will check the latest version and download the latest version if there is a newer version of the ABP CLI extensions.
+* `--skip-cli-version-check` or `-scvc`: Skips checking the latest version of the ABP CLI. If you don't specify, it will check the latest version and shows a warning message if there is a newer version of the ABP CLI.
+- `--skip-extension-version-check` or `-sevc`: Skips checking the latest version of the ABP CLI extensions. If you don't specify, it will check the latest version and download the latest version if there is a newer version of the ABP CLI extensions.
* `--old`: ABP CLI has two variations: `Volo.Abp.Studio.Cli` and `Volo.Abp.Cli`. New features/templates are added to the `Volo.Abp.Studio.Cli`. But if you want to use the old version, you can use this option **at the end of your commands**. For example, `abp new Acme.BookStore --old`.
* `--help` or `-h`: Shows help for the specified command.
## Commands
-Here, is the list of all available commands before explaining their details:
+Here is the list of all available commands before explaining their details:
* **[`help`](../cli#help)**: Shows help on the usage of the ABP CLI.
* **[`cli`](../cli#cli)**: Update or remove ABP CLI.
@@ -358,7 +354,7 @@ Note that this command can upgrade your solution from a previous version, and al
* `--solution-name` or `-sn`: Specify the solution name. Search `*.sln` files in the directory by default.
* `--check-all`: Check the new version of each package separately. Default is `false`.
* `--version` or `-v`: Specifies the version to use for update. If not specified, latest version is used.
-* * `--leptonx-version` or `-lv`: Specifies the LeptonX version to use for update. If not specified, latest version or the version that is compatible with `--version` argument is used.
+* `--leptonx-version` or `-lv`: Specifies the LeptonX version to use for update. If not specified, latest version or the version that is compatible with `--version` argument is used.
### clean
diff --git a/docs/en/contribution/angular-ui.md b/docs/en/contribution/angular-ui.md
index 6aefa43fa8..e3445b12bd 100644
--- a/docs/en/contribution/angular-ui.md
+++ b/docs/en/contribution/angular-ui.md
@@ -12,7 +12,7 @@
- Dotnet core SDK https://dotnet.microsoft.com/en-us/download
- Nodejs LTS https://nodejs.org/en/
- Docker https://docs.docker.com/engine/install
-- Angular CLI. https://angular.io/guide/what-is-angular#angular-cli
+- Angular CLI. https://angular.dev/tools/cli
- Abp CLI https://docs.abp.io/en/abp/latest/cli
- A code editor
diff --git a/docs/en/docs-nav.json b/docs/en/docs-nav.json
index 6fa1f5e620..08b4553d64 100644
--- a/docs/en/docs-nav.json
+++ b/docs/en/docs-nav.json
@@ -552,6 +552,24 @@
"text": "Audit Logging",
"path": "framework/infrastructure/audit-logging.md"
},
+ {
+ "text": "Artificial Intelligence",
+ "items":[
+ {
+ "text": "Overview",
+ "path": "framework/infrastructure/artificial-intelligence/index.md",
+ "isIndex": true
+ },
+ {
+ "text": "Microsoft.Extensions.AI",
+ "path": "framework/infrastructure/artificial-intelligence/microsoft-extensions-ai.md"
+ },
+ {
+ "text": "Semantic Kernel",
+ "path": "framework/infrastructure/artificial-intelligence/microsoft-semantic-kernel.md"
+ }
+ ]
+ },
{
"text": "Background Jobs",
"items": [
@@ -1539,6 +1557,10 @@
"text": "Service Proxies",
"path": "framework/ui/angular/service-proxies.md"
},
+ {
+ "text": "SSR Configuration",
+ "path": "framework/ui/angular/ssr-configuration.md"
+ },
{
"text": "PWA Configuration",
"path": "framework/ui/angular/pwa-configuration.md"
@@ -1623,7 +1645,7 @@
"path": "framework/ui/angular/list-service.md"
},
{
- "text": "Easy *ngFor trackBy",
+ "text": "Easy @for() track",
"path": "framework/ui/angular/track-by-service.md"
},
{
diff --git a/docs/en/framework/architecture/domain-driven-design/repositories.md b/docs/en/framework/architecture/domain-driven-design/repositories.md
index a5753e3808..eed0529112 100644
--- a/docs/en/framework/architecture/domain-driven-design/repositories.md
+++ b/docs/en/framework/architecture/domain-driven-design/repositories.md
@@ -254,6 +254,35 @@ ABP uses dynamic proxying to make these attributes work. There are some rules he
> Change tracking behavior doesn't affect tracking entity objects returned from `InsertAsync` and `UpdateAsync` methods. The objects returned from these methods are always tracked (if the underlying provider has the change tracking feature) and any change you make to these objects are saved into the database.
+#### Check If Change Tracking Is Enabled
+
+In case of you need to check if change tracking is enabled or disabled on a repository object, you can simply read the `IsChangeTrackingEnabled` property. It is `false` by default for read only repositories (see the *Read Only Repositories* section below). It is `null` by default for other repository objects. If it is `null`, change tracking is enabled unless you've explicitly used the change tracking attributes (see the *Attributes for Change Tracking* section).
+
+### The `EntityName` Property
+
+The `EntityName` property is to set the related entity's name on the repository object in some advanced scenarios. For example, you can use this property to use the [Shared-type entity types](https://learn.microsoft.com/en-us/ef/core/modeling/entity-types?tabs=data-annotations#shared-type-entity-types) feature of Entity Framework Core (it allows you to use a single entity class to work on multiple tables in the database). In other cases, you can just ignore it.
+
+Default value is `null` unless you explicitly set it.
+
+**Example usage:**
+
+````csharp
+IRepository _repository; // You can inject it into your class
+...
+_repository.SetEntityName("Product"); //Set the entity name before using the repository
+//use the _repository object as always
+````
+
+### The `ProviderName` Property
+
+The `ProviderName` property of a repository object returns the underlying database provider name. It may return one of the following string values for the built-in providers:
+
+* `Volo.Abp.EntityFrameworkCore` (from the constant `AbpEfCoreConsts.ProviderName` value)
+* `Volo.Abp.MongoDB` (from the constant `AbpMongoDbConsts.ProviderName` value)
+* `Volo.Abp.MemoryDb` (from the constant `AbpMemoryDbConsts.ProviderName` value)
+
+This property is not used in most cases. It is mainly available for internal usage of the ABP framework.
+
## Other Generic Repository Types
Standard `IRepository` interface exposes the standard `IQueryable` and you can freely query using the standard LINQ methods. This is fine for most of the applications. However, some ORM providers or database systems may not support standard `IQueryable` interface. If you want to use such providers, you can't rely on the `IQueryable`.
diff --git a/docs/en/framework/data/entity-framework-core/index.md b/docs/en/framework/data/entity-framework-core/index.md
index 208baeefda..418c040565 100644
--- a/docs/en/framework/data/entity-framework-core/index.md
+++ b/docs/en/framework/data/entity-framework-core/index.md
@@ -146,7 +146,7 @@ Configure(options =>
});
````
-Add actions for the `ConfigureConventions` and `OnModelCreating` methods of the `DbContext` as shown below:
+Add actions for the `ConfigureConventions`, `OnModelCreating` and `OnConfiguring` methods of the `DbContext` as shown below:
````csharp
Configure(options =>
@@ -170,6 +170,15 @@ Configure(options =>
{
// This action is called for OnModelCreating method of specific DbContext.
});
+
+ options.ConfigureDefaultOnConfiguring((dbContext, optionsBuilder) =>
+ {
+ // This action is called for OnConfiguring method of all DbContexts.
+ });
+ options.ConfigureOnConfiguring((dbContext, optionsBuilder) =>
+ {
+ // This action is called for OnConfiguring method of specific DbContext.
+ });
});
````
diff --git a/docs/en/framework/data/entity-framework-core/migrations.md b/docs/en/framework/data/entity-framework-core/migrations.md
index 173fc32d4b..da87cfd26c 100644
--- a/docs/en/framework/data/entity-framework-core/migrations.md
+++ b/docs/en/framework/data/entity-framework-core/migrations.md
@@ -80,15 +80,15 @@ Every module uses its **own databases tables**. For example, the [Identity Modul
Since it is allowed to share a single database by all modules (it is the default configuration), a module typically uses a **table name prefix** to group its own tables.
-The fundamental modules, like [Identity](../../../modules/identity.md), [Tenant Management](../../../modules/tenant-management.md) and [Audit Logs](../../../modules/audit-logging.md), use the `Abp` prefix, while some other modules use their own prefixes. [Identity Server](../../../modules/identity-server.md) module uses the `IdentityServer` prefix for example.
+The fundamental modules, like [Identity](../../../modules/identity.md), [Tenant Management](../../../modules/tenant-management.md) and [Audit Logs](../../../modules/audit-logging.md), use the `Abp` prefix, while some other modules use their own prefixes. [OpenIddict](../../../modules/openiddict.md) module uses the `OpenIddict` prefix for example.
If you want, you can **change the database table name prefix** for a module for your application. Example:
````csharp
-Volo.Abp.IdentityServer.AbpIdentityServerDbProperties.DbTablePrefix = "Ids";
+Volo.Abp.OpenIddict.AbpOpenIddictDbProperties.DbTablePrefix = "Auth";
````
-This code changes the prefix of the [Identity Server](../../../modules/identity-server.md) module. Write this code **at the very beginning** in your application.
+This code changes the prefix of the [OpenIddict](../../../modules/openiddict.md) module. Write this code **at the very beginning** in your application.
> Every module also defines `DbSchema` property (near to `DbTablePrefix`), so you can set it for the databases support the schema usage.
diff --git a/docs/en/framework/data/entity-framework-core/mysql.md b/docs/en/framework/data/entity-framework-core/mysql.md
index 65bc1cb3b1..f5254e2419 100644
--- a/docs/en/framework/data/entity-framework-core/mysql.md
+++ b/docs/en/framework/data/entity-framework-core/mysql.md
@@ -32,11 +32,22 @@ Find `UseSqlServer()` calls in your solution. Check the following files:
Alternatively, you can use the [Pomelo.EntityFrameworkCore.MySql](https://www.nuget.org/packages/Pomelo.EntityFrameworkCore.MySql) provider. Replace the [Volo.Abp.EntityFrameworkCore.MySQL](https://www.nuget.org/packages/Volo.Abp.EntityFrameworkCore.MySQL) package with the [Volo.Abp.EntityFrameworkCore.MySQL.Pomelo](https://www.nuget.org/packages/Volo.Abp.EntityFrameworkCore.MySQL.Pomelo) package in your `.EntityFrameworkCore` project.
-Find ***YourProjectName*EntityFrameworkCoreModule** class inside the `.EntityFrameworkCore` project, replace `typeof(AbpEntityFrameworkCoreMySQLModule)` with `typeof(AbpEntityFrameworkCoreMySQLPomeloModule)` in the `DependsOn` attribute.
+To complete the switch to the Pomelo Provider, you'll need to update your module dependencies. To do that, find ***YourProjectName*EntityFrameworkCoreModule** class inside the `.EntityFrameworkCore` project, replace `typeof(AbpEntityFrameworkCoreMySQLModule)` with `typeof(AbpEntityFrameworkCoreMySQLPomeloModule)` in the `DependsOn` attribute.
-> Depending on your solution structure, you may find more code files need to be changed.
+Also, if you are switching from a provider other than ABP's MySQL provider, you need to call the `UseMySQL` method in the relevant places, as described in the next section.
+
+### UseMySQL()
+
+Find `UseSqlServer()` calls in your solution. Check the following files:
-The `UseMySQL()` method calls remain the same, no changes needed.
+* *YourProjectName*EntityFrameworkCoreModule.cs inside the `.EntityFrameworkCore` project. Replace `UseSqlServer()` with `UseMySql()`.
+* *YourProjectName*DbContextFactory.cs inside the `.EntityFrameworkCore` project. Replace `UseSqlServer()` with `UseMySql()`.
+
+You also need to specify the `ServerVersion`. See https://github.com/PomeloFoundation/Pomelo.EntityFrameworkCore.MySql/wiki/Configuration-Options#server-version for more details.
+
+`UseMySql(configuration.GetConnectionString("Default"), ServerVersion.AutoDetect(configuration.GetConnectionString("Default")));` or `UseMySql(configuration.GetConnectionString("Default"), new MySqlServerVersion(new Version(8, 4, 6)));`
+
+> Depending on your solution structure, you may find more code files need to be changed.
## Change the Connection Strings
diff --git a/docs/en/framework/fundamentals/authorization.md b/docs/en/framework/fundamentals/authorization.md
index 0dae7bbf13..1a104ef420 100644
--- a/docs/en/framework/fundamentals/authorization.md
+++ b/docs/en/framework/fundamentals/authorization.md
@@ -466,14 +466,7 @@ public static class CurrentUserExtensions
}
```
-> If you use Identity Server please add your claims to `RequestedClaims` of `AbpClaimsServiceOptions`.
-
-```csharp
-Configure(options =>
-{
- options.RequestedClaims.AddRange(new[]{ "SocialSecurityNumber" });
-});
-```
+> If you use OpenIddict please see [Updating Claims in Access Token and ID Token](../../modules/openiddict#updating-claims-in-access_token-and-id_token).
## See Also
diff --git a/docs/en/framework/infrastructure/artificial-intelligence.md b/docs/en/framework/infrastructure/artificial-intelligence.md
deleted file mode 100644
index 652c7c8233..0000000000
--- a/docs/en/framework/infrastructure/artificial-intelligence.md
+++ /dev/null
@@ -1,307 +0,0 @@
-# Artificial Intelligence
-
-ABP provides a simple way to integrate AI capabilities into your applications by unifying two popular .NET AI stacks under a common concept called a "workspace":
-
-- Microsoft.Extensions.AI `IChatClient`
-- Microsoft.SemanticKernel `Kernel`
-
-A workspace is just a named scope. You configure providers per workspace and then resolve either default services (for the "Default" workspace) or workspace-scoped services.
-
-## Installation
-
-> This package is not included by default. Install it to enable AI features.
-
-It is suggested to use the ABP CLI to install the package. Open a command line window in the folder of the project (.csproj file) and type the following command:
-
-```bash
-abp add-package Volo.Abp.AI
-```
-
-### Manual Installation
-
-Add nuget package to your project:
-
-```bash
-dotnet add package Volo.Abp.AI
-```
-
-Then add the module dependency to your module class:
-
-```csharp
-using Volo.Abp.AI;
-using Volo.Abp.Modularity;
-
-[DependsOn(typeof(AbpAIModule))]
-public class MyProjectModule : AbpModule
-{
-}
-```
-
-## Usage
-
-### Chat Client
-
-#### Default configuration (quick start)
-
-Configure the default workspace to inject `IChatClient` directly.
-
-```csharp
-using Microsoft.Extensions.AI;
-using Microsoft.SemanticKernel;
-using Volo.Abp.AI;
-using Volo.Abp.Modularity;
-
-public class MyProjectModule : AbpModule
-{
- public override void ConfigureServices(ServiceConfigurationContext context)
- {
- context.Services.PreConfigure(options =>
- {
- options.Workspaces.ConfigureDefault(configuration =>
- {
- configuration.ConfigureChatClient(chatClientConfiguration =>
- {
- chatClientConfiguration.Builder = new ChatClientBuilder(
- sp => new OllamaApiClient("http://localhost:11434", "mistral")
- );
- });
-
- // Chat client only in this quick start
- });
- });
- }
-}
-```
-
-Once configured, inject the default chat client:
-
-```csharp
-using Microsoft.Extensions.AI;
-
-public class MyService
-{
- private readonly IChatClient _chatClient; // default chat client
-
- public MyService(IChatClient chatClient)
- {
- _chatClient = chatClient;
- }
-}
-```
-
-#### Workspace configuration
-
-Workspaces allow multiple, isolated AI configurations. Define workspace types (optionally decorated with `WorkspaceNameAttribute`). If omitted, the type’s full name is used.
-
-```csharp
-using Volo.Abp.AI;
-
-[WorkspaceName("GreetingAssistant")]
-public class GreetingAssistant // ChatClient-only workspace
-{
-}
-```
-
-Configure a ChatClient workspace:
-
-```csharp
-public class MyProjectModule : AbpModule
-{
- public override void ConfigureServices(ServiceConfigurationContext context)
- {
- context.Services.PreConfigure(options =>
- {
- options.Workspaces.Configure(configuration =>
- {
- configuration.ConfigureChatClient(chatClientConfiguration =>
- {
- chatClientConfiguration.Builder = new ChatClientBuilder(
- sp => new OllamaApiClient("http://localhost:11434", "mistral")
- );
-
- chatClientConfiguration.BuilderConfigurers.Add(builder =>
- {
- // Anything you want to do with the builder:
- // builder.UseFunctionInvocation().UseLogging(); // For example
- });
- });
- });
- });
- }
-}
-```
-
-### Semantic Kernel
-
-#### Default configuration
-
-
-```csharp
-public class MyProjectModule : AbpModule
-{
- public override void ConfigureServices(ServiceConfigurationContext context)
- {
- context.Services.PreConfigure(options =>
- {
- options.Workspaces.ConfigureDefault(configuration =>
- {
- configuration.ConfigureKernel(kernelConfiguration =>
- {
- kernelConfiguration.Builder = Kernel.CreateBuilder()
- .AddAzureOpenAIChatClient("...", "...");
- });
- // Note: Chat client is not configured here
- });
- });
- }
-}
-```
-
-Once configured, inject the default kernel:
-
-```csharp
-using System.Threading.Tasks;
-using Volo.Abp.AI;
-
-public class MyService
-{
- private readonly IKernelAccessor _kernelAccessor;
- public MyService(IKernelAccessor kernelAccessor)
- {
- _kernelAccessor = kernelAccessor;
- }
-
- public async Task DoSomethingAsync()
- {
- var kernel = _kernelAccessor.Kernel; // Kernel might be null if no workspace is configured.
-
- var result = await kernel.InvokeAsync(/*... */);
- }
-}
-```
-
-#### Workspace configuration
-
-```csharp
-public class MyProjectModule : AbpModule
-{
- public override void ConfigureServices(ServiceConfigurationContext context)
- {
- context.Services.PreConfigure(options =>
- {
- options.Workspaces.Configure(configuration =>
- {
- configuration.ConfigureKernel(kernelConfiguration =>
- {
- kernelConfiguration.Builder = Kernel.CreateBuilder()
- .AddOpenAIChatCompletion("...", "...");
- });
- });
- });
- }
-}
-```
-
-#### Workspace usage
-
-```csharp
-using Microsoft.Extensions.AI;
-using Volo.Abp.AI;
-using Microsoft.SemanticKernel;
-
-public class PlanningService
-{
- private readonly IKernelAccessor _kernelAccessor;
- private readonly IChatClient _chatClient; // available even if only Kernel is configured
-
- public PlanningService(
- IKernelAccessor kernelAccessor,
- IChatClient chatClient)
- {
- _kernelAccessor = kernelAccessor;
- _chatClient = chatClient;
- }
-
- public async Task PlanAsync(string topic)
- {
- var kernel = _kernelAccessor.Kernel; // Microsoft.SemanticKernel.Kernel
- // Use Semantic Kernel APIs if needed...
-
- var response = await _chatClient.GetResponseAsync(
- [new ChatMessage(ChatRole.User, $"Create a content plan for: {topic}")]
- );
- return response?.Message?.Text ?? string.Empty;
- }
-}
-```
-
-## Options
-
-`AbpAIOptions` configuration pattern offers `ConfigureChatClient(...)` and `ConfigureKernel(...)` methods for configuration. These methods are defined in the `WorkspaceConfiguration` class. They are used to configure the `ChatClient` and `Kernel` respectively.
-
-`Builder` is set once and is used to build the `ChatClient` or `Kernel` instance. `BuilderConfigurers` is a list of actions that are applied to the `Builder` instance for incremental changes. These actions are executed in the order they are added.
-
-If a workspace configures only the Kernel, a chat client may still be exposed for that workspace through the Kernel’s service provider (when available).
-
-
-## Advanced Usage and Customizations
-
-### Addding Your Own DelegatingChatClient
-
-If you want to build your own decorator, implement a `DelegatingChatClient` derivative and provide an extension method that adds it to the `ChatClientBuilder` using `builder.Use(...)`.
-
-Example sketch:
-
-```csharp
-using Microsoft.Extensions.AI;
-
-public class SystemMessageChatClient : DelegatingChatClient
-{
- public SystemMessageChatClient(IChatClient inner, string systemMessage) : base(inner)
- {
- SystemMessage = systemMessage;
- }
-
- public string SystemMessage { get; set; }
-
- public override Task GetResponseAsync(IEnumerable messages, ChatOptions? options = null, CancellationToken cancellationToken = default)
- {
- // Mutate messages/options as needed, then call base
- return base.GetResponseAsync(messages, options, cancellationToken);
- }
-}
-
-public static class SystemMessageChatClientExtensions
-{
- public static ChatClientBuilder UseSystemMessage(this ChatClientBuilder builder, string systemMessage)
- {
- return builder.Use(client => new SystemMessageChatClient(client, systemMessage));
- }
-}
-```
-
-
-```cs
-chatClientConfiguration.BuilderConfigurers.Add(builder =>
-{
- builder.UseSystemMessage("You are a helpful assistant that greets users in a friendly manner with their names.");
-});
-```
-
-## Technical Anatomy
-
-- `AbpAIModule`: Wires up configured workspaces, registers keyed services and default services for the `"Default"` workspace.
-- `AbpAIOptions`: Holds `Workspaces` and provides helper methods for internal keyed service naming.
-- `WorkspaceConfigurationDictionary` and `WorkspaceConfiguration`: Configure per-workspace Chat Client and Kernel.
-- `ChatClientConfiguration` and `KernelConfiguration`: Hold builders and a list of ordered builder configurers.
-- `WorkspaceNameAttribute`: Names a workspace; falls back to the type’s full name if not specified.
-- `IChatClient`: Typed chat client for a workspace.
-- `IKernelAccessor`: Provides access to the workspace’s `Kernel` instance if configured.
-- `AbpAIWorkspaceOptions`: Exposes `ConfiguredWorkspaceNames` for diagnostics.
-
-There are no database tables for this feature; it is a pure configuration and DI integration layer.
-
-## See Also
-
-- Microsoft.Extensions.AI (Chat Client)
-- Microsoft Semantic Kernel
\ No newline at end of file
diff --git a/docs/en/framework/infrastructure/artificial-intelligence/index.md b/docs/en/framework/infrastructure/artificial-intelligence/index.md
new file mode 100644
index 0000000000..bdd1125e9d
--- /dev/null
+++ b/docs/en/framework/infrastructure/artificial-intelligence/index.md
@@ -0,0 +1,38 @@
+```json
+//[doc-seo]
+{
+ "Description": "Explore ABP Framework's AI integration, enabling seamless AI capabilities, workspace management, and reusable modules for .NET developers."
+}
+```
+
+# Artificial Intelligence (AI)
+ABP Framework provides integration for AI capabilities to your application by using Microsoft's popular AI libraries. The main purpose of this integration is to provide a consistent and easy way to use AI capabilities and manage different AI providers, models and configurations in a single application.
+
+ABP introduces a concept called **AI Workspace**. A workspace allows you to configure isolated AI configurations for a named scope. You can then resolve AI services for a specific workspace when you need to use them.
+
+> ABP Framework can work with any AI library or framework that supports .NET development. However, the AI integration features explained in the following documents provide a modular and standard way to work with AI, which allows ABP developers to create reusable modules and components with AI capabilities in a standard way.
+
+## Installation
+
+Use the [ABP CLI](../../../cli/index.md) to install the [Volo.Abp.AI](https://www.nuget.org/packages/Volo.Abp.AI) NuGet package into your project. Open a command line window in the root directory of your project (`.csproj` file) and type the following command:
+
+```bash
+abp add-package Volo.Abp.AI
+```
+
+*For different installation options, check [the package definition page](https://abp.io/package-detail/Volo.Abp.AI).*
+
+## Usage
+
+The `Volo.Abp.AI` package provides integration with the following libraries:
+
+* [Microsoft.Extensions.AI](https://learn.microsoft.com/en-us/dotnet/ai/microsoft-extensions-ai)
+* [Microsoft.SemanticKernel](https://learn.microsoft.com/en-us/semantic-kernel/overview/)
+
+The Microsoft.Extensions.AI library is suggested for library developers to keep the library dependency minimum and simple (since it provides basic abstractions and fundamental AI provider integrations), while Semantic Kernel is suggested for applications that need rich and advanced AI integration features.
+
+Check the following documentation to learn how to use these libraries with the ABP integration:
+
+- [ABP Microsoft.Extensions.AI integration](./microsoft-extensions-ai.md)
+- [ABP Microsoft.SemanticKernel integration](./microsoft-semantic-kernel.md)
+
diff --git a/docs/en/framework/infrastructure/artificial-intelligence/microsoft-extensions-ai.md b/docs/en/framework/infrastructure/artificial-intelligence/microsoft-extensions-ai.md
new file mode 100644
index 0000000000..35b370585e
--- /dev/null
+++ b/docs/en/framework/infrastructure/artificial-intelligence/microsoft-extensions-ai.md
@@ -0,0 +1,176 @@
+# Microsoft.Extensions.AI
+[Microsoft.Extensions.AI](https://learn.microsoft.com/en-us/dotnet/ai/microsoft-extensions-ai) is a library that provides a unified API for integrating AI services. It is a part of the Microsoft AI Extensions Library. It is used to integrate AI services into your application. This documentation is about the usage of this library with ABP Framework. Make sure you have read the [Artificial Intelligence](./index.md) documentation before reading this documentation.
+
+## Usage
+
+You can resolve `IChatClient` to access configured chat client from your service and use it directly.
+
+```csharp
+public class MyService
+{
+ private readonly IChatClient _chatClient;
+ public MyService(IChatClient chatClient)
+ {
+ _chatClient = chatClient;
+ }
+
+ public async Task GetResponseAsync(string prompt)
+ {
+ return await _chatClient.GetResponseAsync(prompt);
+ }
+}
+```
+
+You can also resolve `IChatClientAccessor` to access the `IChatClient` optionally configured scenarios such as developing a module or a service that may use AI capabilities **optionally**.
+
+
+```csharp
+public class MyService
+{
+ private readonly IChatClientAccessor _chatClientAccessor;
+ public MyService(IChatClientAccessor chatClientAccessor)
+ {
+ _chatClientAccessor = chatClientAccessor;
+ }
+
+ public async Task GetResponseAsync(string prompt)
+ {
+ var chatClient = _chatClientAccessor.ChatClient;
+ if (chatClient is null)
+ {
+ return "No chat client configured";
+ }
+ return await chatClient.GetResponseAsync(prompt);
+ }
+}
+```
+
+### Workspaces
+
+Workspaces are a way to configure isolated AI configurations for a named scope. You can define a workspace by decorating a class with the `WorkspaceNameAttribute` attribute that carries the workspace name.
+- Workspace names must be unique.
+- Workspace names cannot contain spaces _(use underscores or camelCase)_.
+- Workspace names are case-sensitive.
+
+```csharp
+using Volo.Abp.AI;
+
+[WorkspaceName("CommentSummarization")]
+public class CommentSummarization
+{
+}
+```
+
+> [!NOTE]
+> If you don't specify the workspace name, the full name of the class will be used as the workspace name.
+
+You can resolve generic versions of `IChatClient` and `IChatClientAccessor` services for a specific workspace as generic arguments. If Chat Client is not configured for a workspace, you will get `null` from the accessor services. You should check the accessor before using it. This applies only for specified workspaces. Another workspace may have a configured Chat Client.
+
+`IChatClient` or `IChatClientAccessor` can be resolved to access a specific workspace's chat client. This is a typed chat client and can be configured separately from the default chat client.
+
+
+Example of resolving a typed chat client:
+```csharp
+public class MyService
+{
+ private readonly IChatClient _chatClient;
+
+ public MyService(IChatClient chatClient)
+ {
+ _chatClient = chatClient;
+ }
+
+ public async Task GetResponseAsync(string prompt)
+ {
+ return await _chatClient.GetResponseAsync(prompt);
+ }
+}
+```
+
+Example of resolving a typed chat client accessor:
+```csharp
+public class MyService
+{
+ private readonly IChatClientAccessor _chatClientAccessor;
+}
+ public async Task GetResponseAsync(string prompt)
+ {
+ var chatClient = _chatClientAccessor.ChatClient;
+ if (chatClient is null)
+ {
+ return "No chat client configured";
+ }
+ return await chatClient.GetResponseAsync(prompt);
+ }
+}
+```
+
+## Configuration
+
+`AbpAIWorkspaceOptions` configuration is used to configure AI workspaces and their configurations. You can configure the default workspace and also configure isolated workspaces by using the this options class.It has to be configured **before the services are configured** in the `PreConfigure` method of your module class. It is important since the services are registered after the configuration is applied.
+
+- `AbpAIWorkspaceOptions` has a `Workspaces` property that is type of `WorkspaceConfigurationDictionary` which is a dictionary of workspace names and their configurations. It provides `Configure` and `ConfigureDefault` methods to configure the default workspace and also configure isolated workspaces by using the workspace type.
+
+- Configure method passes `WorkspaceConfiguration` object to the configure action. You can configure the `ChatClient` by using the `ConfigureChatClient` method.
+
+- `ConfigureChatClient()` method passes `ChatClientConfiguration` parameter to the configure action. You can configure the `Builder` and `BuilderConfigurers` by using the `ConfigureBuilder` method.
+ - `Builder` is set once and is used to build the `ChatClient` instance.
+ - `BuilderConfigurers` is a list of actions that are applied to the `Builder` instance for incremental changes.These actions are executed in the order they are added.
+
+To configure a chat client, you'll need a LLM provider package such as [Microsoft.Extensions.AI.OpenAI](https://www.nuget.org/packages/Microsoft.Extensions.AI.OpenAI) or [OllamaSharp](https://www.nuget.org/packages/OllamaSharp/) to configure a chat client.
+
+_The following example requires [OllamaSharp](https://www.nuget.org/packages/OllamaSharp/) package to be installed._
+
+
+Demonstration of the default workspace configuration:
+```csharp
+[DependsOn(typeof(AbpAIModule))]
+public class MyProjectModule : AbpModule
+{
+ public override void PreConfigureServices(ServiceConfigurationContext context)
+ {
+ PreConfigure(options =>
+ {
+ options.Workspaces.ConfigureDefault(configuration =>
+ {
+ configuration.ConfigureChatClient(chatClientConfiguration =>
+ {
+ chatClientConfiguration.Builder = new ChatClientBuilder(
+ sp => new OllamaApiClient("http://localhost:11434", "mistral")
+ );
+ });
+ });
+ });
+ }
+}
+```
+
+
+Demonstration of the isolated workspace configuration:
+```csharp
+[DependsOn(typeof(AbpAIModule))]
+public class MyProjectModule : AbpModule
+{
+ public override void PreConfigureServices(ServiceConfigurationContext context)
+ {
+ PreConfigure(options =>
+ {
+ options.Workspaces.Configure(configuration =>
+ {
+ configuration.ConfigureChatClient(chatClientConfiguration =>
+ {
+ chatClientConfiguration.Builder = new ChatClientBuilder(
+ sp => new OllamaApiClient("http://localhost:11434", "mistral")
+ );
+ });
+ });
+ });
+ }
+}
+```
+
+
+## See Also
+
+- [Usage of Semantic Kernel](./microsoft-semantic-kernel.md)
+- [AI Samples for .NET](https://learn.microsoft.com/en-us/samples/dotnet/ai-samples/ai-samples/)
\ No newline at end of file
diff --git a/docs/en/framework/infrastructure/artificial-intelligence/microsoft-semantic-kernel.md b/docs/en/framework/infrastructure/artificial-intelligence/microsoft-semantic-kernel.md
new file mode 100644
index 0000000000..07622391bd
--- /dev/null
+++ b/docs/en/framework/infrastructure/artificial-intelligence/microsoft-semantic-kernel.md
@@ -0,0 +1,135 @@
+# Microsoft.SemanticKernel
+[Microsoft.SemanticKernel](https://learn.microsoft.com/en-us/semantic-kernel/overview/) is a library that provides a unified SDK for integrating AI services. This documentation is about the usage of this library with ABP Framework. Make sure you have read the [Artificial Intelligence](./index.md) documentation before reading this documentation.
+
+## Usage
+
+Semantic Kernel can be used by resolving `IKernelAccessor` service that carries the `Kernel` instance. Kernel might be `null` if no workspace is configured. You should check the kernel before using it.
+
+```csharp
+public class MyService
+{
+ private readonly IKernelAccessor _kernelAccessor;
+ public MyService(IKernelAccessor kernelAccessor)
+ {
+ _kernelAccessor = kernelAccessor;
+ }
+
+ public async Task GetResponseAsync(string prompt)
+ {
+ var kernel = _kernelAccessor.Kernel;
+ if (kernel is null)
+ {
+ return "No kernel configured";
+ }
+ return await kernel.InvokeAsync(prompt);
+ }
+}
+```
+
+### Workspaces
+
+Workspaces are a way to configure isolated AI configurations for a named scope. You can define a workspace by decorating a class with the `WorkspaceNameAttribute` attribute that carries the workspace name.
+- Workspace names must be unique.
+- Workspace names cannot contain spaces _(use underscores or camelCase)_.
+- Workspace names are case-sensitive.
+
+```csharp
+using Volo.Abp.AI;
+
+[WorkspaceName("CommentSummarization")]
+public class CommentSummarization
+{
+}
+```
+
+> [!NOTE]
+> If you don't specify the workspace name, the full name of the class will be used as the workspace name.
+
+You can resolve generic versions of `IKernelAccessor` service for a specific workspace as generic arguments. If Kernel is not configured for a workspace, you will get `null` from the accessor service. You should check the accessor before using it. This applies only for specified workspaces. Another workspace may have a configured Kernel.
+
+
+`IKernelAccessor` can be resolved to access a specific workspace's kernel. This is a typed kernel accessor and each workspace can have its own kernel configuration.
+
+Example of resolving a typed kernel accessor:
+```csharp
+public class MyService
+{
+ private readonly IKernelAccessor _kernelAccessor;
+}
+ public async Task GetResponseAsync(string prompt)
+ {
+ var kernel = _kernelAccessor.Kernel;
+ if (kernel is null)
+ {
+ return "No kernel configured";
+ }
+ return await kernel.InvokeAsync(prompt);
+ }
+}
+```
+
+## Configuration
+
+`AbpAIWorkspaceOptions` configuration is used to configure AI workspaces and their configurations. You can configure the default workspace and also configure isolated workspaces by using the this options class.It has to be configured **before the services are configured** in the `PreConfigure` method of your module class. It is important since the services are registered after the configuration is applied.
+
+- `AbpAIWorkspaceOptions` has a `Workspaces` property that is type of `WorkspaceConfigurationDictionary` which is a dictionary of workspace names and their configurations. It provides `Configure` and `ConfigureDefault` methods to configure the default workspace and also configure isolated workspaces by using the workspace type.
+
+- Configure method passes `WorkspaceConfiguration` object to the configure action. You can configure the `Kernel` by using the `ConfigureKernel` method.
+
+- `ConfigureKernel()` method passes `KernelConfiguration` parameter to the configure action. You can configure the `Builder` and `BuilderConfigurers` by using the `ConfigureBuilder` method.
+ - `Builder` is set once and is used to build the `Kernel` instance.
+ - `BuilderConfigurers` is a list of actions that are applied to the `Builder` instance for incremental changes.These actions are executed in the order they are added.
+
+To configure a kernel, you'll need a kernel connector package such as [Microsoft.SemanticKernel.Connectors.OpenAI](Microsoft.SemanticKernel.Connectors.OpenAI) to configure a kernel to use a specific LLM provider.
+
+_The following example requires [Microsoft.SemanticKernel.Connectors.AzureOpenAI](Microsoft.SemanticKernel.Connectors.AzureOpenAI) package to be installed._
+
+Demonstration of the default workspace configuration:
+```csharp
+[DependsOn(typeof(AbpAIModule))]
+public class MyProjectModule : AbpModule
+{
+ public override void PreConfigureServices(ServiceConfigurationContext context)
+ {
+ PreConfigure(options =>
+ {
+ options.Workspaces.ConfigureDefault(configuration =>
+ {
+ configuration.ConfigureKernel(kernelConfiguration =>
+ {
+ kernelConfiguration.Builder = Kernel.CreateBuilder()
+ .AddAzureOpenAIChatClient("...", "...");
+ });
+ // Note: Chat client is not configured here
+ });
+ });
+ }
+}
+```
+
+Demonstration of the isolated workspace configuration:
+```csharp
+[DependsOn(typeof(AbpAIModule))]
+public class MyProjectModule : AbpModule
+{
+ public override void PreConfigureServices(ServiceConfigurationContext context)
+ {
+ PreConfigure(options =>
+ {
+ options.Workspaces.Configure(configuration =>
+ {
+ configuration.ConfigureKernel(kernelConfiguration =>
+ {
+ kernelConfiguration.Builder = Kernel.CreateBuilder()
+ .AddAzureOpenAIChatClient("...", "...");
+ });
+ });
+ });
+ }
+}
+```
+
+## See Also
+
+- [Usage of Microsoft.Extensions.AI](./microsoft-extensions-ai.md)
+- [AI Samples for .NET](https://learn.microsoft.com/en-us/samples/dotnet/ai-samples/ai-samples/)
\ No newline at end of file
diff --git a/docs/en/framework/infrastructure/event-bus/distributed/azure.md b/docs/en/framework/infrastructure/event-bus/distributed/azure.md
index 8e1bff3e63..92a961230d 100644
--- a/docs/en/framework/infrastructure/event-bus/distributed/azure.md
+++ b/docs/en/framework/infrastructure/event-bus/distributed/azure.md
@@ -137,4 +137,14 @@ Configure(options =>
});
````
+Use `TokenCredential` instead of `ConnectionString` if you want to use custom credential.
+
+````csharp
+Configure(options =>
+{
+ options.Connections.Default.FullyQualifiedNamespace = "sb-my-app.servicebus.windows.net";
+ options.Connections.Default.TokenCredential = new DefaultAzureCredential();
+});
+````
+
Using these options classes can be combined with the `appsettings.json` way. Configuring an option property in the code overrides the value in the configuration file.
diff --git a/docs/en/framework/infrastructure/index.md b/docs/en/framework/infrastructure/index.md
index a242c8b4fa..ec6377d757 100644
--- a/docs/en/framework/infrastructure/index.md
+++ b/docs/en/framework/infrastructure/index.md
@@ -10,7 +10,7 @@
ABP provides a complete infrastructure for creating real world software solutions with modern architectures based on the .NET platform. Each of the following documents explains an infrastructure feature:
* [Audit Logging](./audit-logging.md)
-* [Artificial Intelligence](./artificial-intelligence.md)
+* [Artificial Intelligence](./artificial-intelligence/index.md)
* [Background Jobs](./background-jobs/index.md)
* [Background Workers](./background-workers/index.md)
* [BLOB Storing](./blob-storing/index.md)
diff --git a/docs/en/framework/ui/angular/component-replacement.md b/docs/en/framework/ui/angular/component-replacement.md
index 6feebfc409..ec1102f893 100644
--- a/docs/en/framework/ui/angular/component-replacement.md
+++ b/docs/en/framework/ui/angular/component-replacement.md
@@ -584,8 +584,8 @@ Open the generated `nav-items.component.html` in `src/app/nav-items` folder and
class="bg-transparent border-0 text-white"
/>
```
diff --git a/docs/en/framework/ui/angular/data-table-column-extensions.md b/docs/en/framework/ui/angular/data-table-column-extensions.md
index 30b9facf0d..0365336d81 100644
--- a/docs/en/framework/ui/angular/data-table-column-extensions.md
+++ b/docs/en/framework/ui/angular/data-table-column-extensions.md
@@ -171,7 +171,7 @@ It has the following properties:
- **index** is the table index where the record is at.
-- **getInjected** is the equivalent of [Injector.get](https://angular.io/api/core/Injector#get). You can use it to reach injected dependencies of `ExtensibleTableComponent`, including, but not limited to, its parent component.
+- **getInjected** is the equivalent of [Injector.get](https://angular.dev/api/core/Injector). You can use it to reach injected dependencies of `ExtensibleTableComponent`, including, but not limited to, its parent component.
```js
{
diff --git a/docs/en/framework/ui/angular/dynamic-form-extensions.md b/docs/en/framework/ui/angular/dynamic-form-extensions.md
index ee7af81397..a92a06d609 100644
--- a/docs/en/framework/ui/angular/dynamic-form-extensions.md
+++ b/docs/en/framework/ui/angular/dynamic-form-extensions.md
@@ -107,7 +107,7 @@ Extra properties defined on an existing entity will be included in the create an
It has the following properties:
-- **getInjected** is the equivalent of [Injector.get](https://angular.io/api/core/Injector#get). You can use it to reach injected dependencies of `ExtensibleFormPropComponent`, including, but not limited to, its parent components.
+- **getInjected** is the equivalent of [Injector.get](https://angular.dev/api/core/Injector). You can use it to reach injected dependencies of `ExtensibleFormPropComponent`, including, but not limited to, its parent components.
```js
{
diff --git a/docs/en/framework/ui/angular/entity-action-extensions.md b/docs/en/framework/ui/angular/entity-action-extensions.md
index 152ff6636d..5a8e74a2f9 100644
--- a/docs/en/framework/ui/angular/entity-action-extensions.md
+++ b/docs/en/framework/ui/angular/entity-action-extensions.md
@@ -272,7 +272,7 @@ It has the following properties:
- **index** is the table index where the record is at.
-- **getInjected** is the equivalent of [Injector.get](https://angular.io/api/core/Injector#get). You can use it to reach injected dependencies of `GridActionsComponent`, including, but not limited to, its parent component.
+- **getInjected** is the equivalent of [Injector.get](https://angular.dev/api/core/Injector). You can use it to reach injected dependencies of `GridActionsComponent`, including, but not limited to, its parent component.
```js
{
diff --git a/docs/en/framework/ui/angular/form-validation.md b/docs/en/framework/ui/angular/form-validation.md
index 35a54549af..b4ed31842d 100644
--- a/docs/en/framework/ui/angular/form-validation.md
+++ b/docs/en/framework/ui/angular/form-validation.md
@@ -52,7 +52,7 @@ export const appConfig: ApplicationConfig = {
};
```
-When a [validator](https://angular.io/guide/form-validation#defining-custom-validators) or an [async validator](https://angular.io/guide/form-validation#creating-asynchronous-validators) returns an error with the key given to the error blueprints (`uniqueUsername` here), the validation library will be able to display an error message after localizing according to the given key and interpolation params. The result will look like this:
+When a [validator](https://angular.dev/guide/forms/form-validation) or an [async validator](https://angular.dev/guide/forms/form-validation) returns an error with the key given to the error blueprints (`uniqueUsername` here), the validation library will be able to display an error message after localizing according to the given key and interpolation params. The result will look like this:
@@ -146,12 +146,13 @@ import { ChangeDetectionStrategy, Component } from "@angular/core";
selector: "app-validation-error",
imports:[CommonModule, LocalizationPipe],
template: `
-
+ }
`,
changeDetection: ChangeDetectionStrategy.OnPush,
})
@@ -250,7 +251,7 @@ buildForm() {
{%{{ 'AbpIdentity::UserInformations' | abpLocalization }}%}
-
+
@@ -263,7 +264,7 @@ buildForm() {
+ />
}
diff --git a/docs/en/framework/ui/angular/http-requests.md b/docs/en/framework/ui/angular/http-requests.md
index 5cb217540d..a5ca0dec66 100644
--- a/docs/en/framework/ui/angular/http-requests.md
+++ b/docs/en/framework/ui/angular/http-requests.md
@@ -9,7 +9,7 @@
## About HttpClient
-Angular has the amazing [HttpClient](https://angular.io/guide/http) for communication with backend services. It is a layer on top and a simplified representation of [XMLHttpRequest Web API](https://developer.mozilla.org/en-US/docs/Web/API/XMLHttpRequest). It also is the recommended agent by Angular for any HTTP request. There is nothing wrong with using the `HttpClient` in your ABP project.
+Angular has the amazing [HttpClient](https://angular.dev/guide/http/making-requests) for communication with backend services. It is a layer on top and a simplified representation of [XMLHttpRequest Web API](https://developer.mozilla.org/en-US/docs/Web/API/XMLHttpRequest). It also is the recommended agent by Angular for any HTTP request. There is nothing wrong with using the `HttpClient` in your ABP project.
However, `HttpClient` leaves error handling to the caller (method). In other words, HTTP errors are handled manually and by hooking into the observer of the `Observable` returned.
@@ -93,7 +93,7 @@ postFoo(body: Foo) {
}
```
-You may [check here](https://github.com/abpframework/abp/blob/dev/npm/ng-packs/packages/core/src/lib/models/rest.ts#L23) for complete `Rest.Request` type, which has only a few changes compared to [HttpRequest](https://angular.io/api/common/http/HttpRequest) class in Angular.
+You may [check here](https://github.com/abpframework/abp/blob/dev/npm/ng-packs/packages/core/src/lib/models/rest.ts#L23) for complete `Rest.Request` type, which has only a few changes compared to [HttpRequest](https://angular.dev/api/common/http/HttpRequest) class in Angular.
### How to Disable Default Error Handler of RestService
diff --git a/docs/en/framework/ui/angular/lazy-load-service.md b/docs/en/framework/ui/angular/lazy-load-service.md
index e0942a15f0..9eb1113899 100644
--- a/docs/en/framework/ui/angular/lazy-load-service.md
+++ b/docs/en/framework/ui/angular/lazy-load-service.md
@@ -44,10 +44,13 @@ The first parameter of `load` method expects a `LoadingStrategy`. If you pass a
```js
import { LazyLoadService, LOADING_STRATEGY } from '@abp/ng.core';
import { inject } from '@angular/core';
+import { AsyncPipe } from '@angular/common';
@Component({
template: `
-
+ @if (libraryLoaded$ | async) {
+
+ }
`
})
class DemoComponent {
@@ -59,7 +62,7 @@ class DemoComponent {
}
```
-The `load` method returns an observable to which you can subscibe in your component or with an `async` pipe. In the example above, the `NgIf` directive will render `` only **if the script gets successfully loaded or is already loaded before**.
+The `load` method returns an observable to which you can subscibe in your component or with an `async` pipe. In the example above, the `@if(...)` directive will render `` only **if the script gets successfully loaded or is already loaded before**.
> You can subscribe multiple times in your template with `async` pipe. The Scripts will only be loaded once.
@@ -74,10 +77,13 @@ If you pass a `StyleLoadingStrategy` instance as the first parameter of `load` m
```js
import { LazyLoadService, LOADING_STRATEGY } from '@abp/ng.core';
import { inject } from '@angular/core';
+import { AsyncPipe } from '@angular/common';
@Component({
template: `
-
+ @if (stylesLoaded$ | async) {
+
+ }
`
})
class DemoComponent {
@@ -89,7 +95,7 @@ class DemoComponent {
}
```
-The `load` method returns an observable to which you can subscibe in your component or with an `AsyncPipe`. In the example above, the `NgIf` directive will render `` only **if the style gets successfully loaded or is already loaded before**.
+The `load` method returns an observable to which you can subscibe in your component or with an `AsyncPipe`. In the example above, the `@if(...)` directive will render `` only **if the style gets successfully loaded or is already loaded before**.
> You can subscribe multiple times in your template with `async` pipe. The styles will only be loaded once.
@@ -126,10 +132,13 @@ A common usecase is **loading multiple scripts and/or styles before using a feat
import { LazyLoadService, LOADING_STRATEGY } from '@abp/ng.core';
import { forkJoin } from 'rxjs';
import { inject } from '@angular/core';
+import { AsyncPipe } from '@angular/common';
@Component({
template: `
-
+ @if (scriptsAndStylesLoaded$ | async) {
+
+ }
`
})
class DemoComponent {
@@ -168,10 +177,13 @@ Another frequent usecase is **loading dependent scripts in order**:
import { LazyLoadService, LOADING_STRATEGY } from '@abp/ng.core';
import { concat } from 'rxjs';
import { inject } from '@angular/core';
+import { AsyncPipe } from '@angular/common';
@Component({
template: `
-
+ @if (scriptsLoaded$ | async) {
+
+ }
`
})
class DemoComponent {
diff --git a/docs/en/framework/ui/angular/list-service.md b/docs/en/framework/ui/angular/list-service.md
index f8b0a42249..dab58d0e33 100644
--- a/docs/en/framework/ui/angular/list-service.md
+++ b/docs/en/framework/ui/angular/list-service.md
@@ -126,7 +126,7 @@ Then you can place inputs to the HTML:
## Usage with Observables
-You may use observables in combination with [AsyncPipe](https://angular.io/guide/observables-in-angular#async-pipe) of Angular instead. Here are some possibilities:
+You may use observables in combination with [AsyncPipe](https://angular.dev/ecosystem/rxjs-interop) of Angular instead. Here are some possibilities:
```js
book$ = this.list.hookToQuery(query => this.bookService.getListByInput(query));
diff --git a/docs/en/framework/ui/angular/localization.md b/docs/en/framework/ui/angular/localization.md
index 034e77abf0..9f3122529c 100644
--- a/docs/en/framework/ui/angular/localization.md
+++ b/docs/en/framework/ui/angular/localization.md
@@ -220,7 +220,7 @@ As of v2.9 ABP supports RTL. If you are generating a new project with v2.9 and a
### Step 1. Create Chunks for Bootstrap LTR and RTL
-Find [styles configuration in angular.json](https://angular.io/guide/workspace-config#style-script-config) and make sure the chunks in your project has `bootstrap-rtl.min` and `bootstrap-ltr.min` as shown below.
+Find [styles configuration in angular.json](https://angular.dev/reference/configs/workspace-config) and make sure the chunks in your project has `bootstrap-rtl.min` and `bootstrap-ltr.min` as shown below.
```json
{
@@ -279,7 +279,7 @@ export class AppComponent {}
## Registering a New Locale
-Since ABP has more than one language, Angular locale files load lazily using [Webpack's import function](https://webpack.js.org/api/module-methods/#import-1) to avoid increasing the bundle size and to register the Angular core using the [`registerLocaleData`](https://angular.io/api/common/registerLocaleData) function. The chunks to be included in the bundle are specified by the [Webpack's magic comments](https://webpack.js.org/api/module-methods/#magic-comments) as hard-coded. Therefore a `registerLocale` function that returns Webpack `import` function must be passed to `provideAbpCore(withOptions({...}))`.
+Since ABP has more than one language, Angular locale files load lazily using [Webpack's import function](https://webpack.js.org/api/module-methods/#import-1) to avoid increasing the bundle size and to register the Angular core using the [`registerLocaleData`](https://angular.dev/api/common/registerLocaleData) function. The chunks to be included in the bundle are specified by the [Webpack's magic comments](https://webpack.js.org/api/module-methods/#magic-comments) as hard-coded. Therefore a `registerLocale` function that returns Webpack `import` function must be passed to `provideAbpCore(withOptions({...}))`.
### registerLocaleFn
diff --git a/docs/en/framework/ui/angular/modifying-the-menu.md b/docs/en/framework/ui/angular/modifying-the-menu.md
index 75da5169cb..eec9e79ba0 100644
--- a/docs/en/framework/ui/angular/modifying-the-menu.md
+++ b/docs/en/framework/ui/angular/modifying-the-menu.md
@@ -44,7 +44,29 @@ export const appConfig: ApplicationConfig = {
Notes
- This approach works across themes. If you are using LeptonX, the brand logo component reads these values automatically; you don't need any theme-specific code.
-- You can still override visuals with CSS variables if desired. See the LeptonX section for CSS overrides.
+- You can still override visuals with CSS variables if desired. See the alternative approach below.
+
+### Alternative: Using CSS Variables (LeptonX Theme)
+
+If you're using the LeptonX theme, you can also configure the logo using CSS variables in your `styles.scss` file. This approach is specific to LeptonX and provides direct control over the logo styling.
+
+Add the following to your `src/styles.scss`:
+
+```scss
+:root {
+ --lpx-logo: url('/assets/images/logo/logo-light.png');
+ --lpx-logo-icon: url('/assets/images/logo/logo-light-thumbnail.png');
+}
+```
+
+**When to use each approach:**
+
+| Approach | Use Case | Theme Support |
+|----------|----------|-------------|
+| **provideLogo** (recommended) | Cross-theme compatibility, environment-based configuration | All themes |
+| **CSS Variables** | LeptonX-specific styling, fine-grained CSS control | LeptonX only |
+
+**Recommendation:** Use the `provideLogo` approach for most cases as it's theme-independent and follows ABP's standard configuration pattern. Use CSS variables only when you need LeptonX-specific styling control or have existing CSS-based theme customizations.
## How to Add a Navigation Element
diff --git a/docs/en/framework/ui/angular/page-toolbar-extensions.md b/docs/en/framework/ui/angular/page-toolbar-extensions.md
index 8214c19889..30c5c9813d 100644
--- a/docs/en/framework/ui/angular/page-toolbar-extensions.md
+++ b/docs/en/framework/ui/angular/page-toolbar-extensions.md
@@ -215,7 +215,7 @@ It has the following properties:
}
```
-- **getInjected** is the equivalent of [Injector.get](https://angular.io/api/core/Injector#get). You can use it to reach injected dependencies of `PageToolbarComponent`, including, but not limited to, its parent component.
+- **getInjected** is the equivalent of [Injector.get](https://angular.dev/api/core/Injector). You can use it to reach injected dependencies of `PageToolbarComponent`, including, but not limited to, its parent component.
```js
{
diff --git a/docs/en/framework/ui/angular/permission-management-component-replacement.md b/docs/en/framework/ui/angular/permission-management-component-replacement.md
index f91fbb42d9..7ee3022b80 100644
--- a/docs/en/framework/ui/angular/permission-management-component-replacement.md
+++ b/docs/en/framework/ui/angular/permission-management-component-replacement.md
@@ -334,7 +334,7 @@ Open the generated `permission-management.component.html` in `src/app/permission
```html
-
+ @if (data.entityDisplayName) {
{%{{{ 'AbpPermissionManagement::Permissions' | abpLocalization }}}%} -
@@ -360,19 +360,22 @@ Open the generated `permission-management.component.html` in `src/app/permission
@@ -393,34 +396,36 @@ Open the generated `permission-management.component.html` in `src/app/permission
}}}%}
-
-
-
-
+ @for (permission of selectedGroupPermissions; track permission.name; let i = $index) {
+
+
+
+
+ }
@@ -433,7 +438,7 @@ Open the generated `permission-management.component.html` in `src/app/permission
'AbpIdentity::Save' | abpLocalization
}}}%}
-
+ }
```
diff --git a/docs/en/framework/ui/angular/pwa-configuration.md b/docs/en/framework/ui/angular/pwa-configuration.md
index 2c042e9d77..ea63f60b96 100644
--- a/docs/en/framework/ui/angular/pwa-configuration.md
+++ b/docs/en/framework/ui/angular/pwa-configuration.md
@@ -37,7 +37,7 @@ Here is the output of the command:
So, Angular CLI updates some files and add a few others:
-- **ngsw-config.json** is where the [service worker configuration](https://angular.io/guide/service-worker-config) is placed. Not all PWAs have this file. It is specific to Angular.
+- **ngsw-config.json** is where the [service worker configuration](https://angular.dev/ecosystem/service-workers/config) is placed. Not all PWAs have this file. It is specific to Angular.
- **manifest.webmanifest** is a [web app manifest](https://developer.mozilla.org/en-US/docs/Web/Manifest) and provides information about your app in JSON format.
- **icons** are placeholder icons that are referred to in your web app manifest. We will replace these in a minute.
- **angular.json** has following modifications:
@@ -45,7 +45,7 @@ So, Angular CLI updates some files and add a few others:
- `serviceWorker` is `true` in production build.
- `ngswConfigPath` refers to _ngsw-config.json_.
- **package.json** has _@angular/service-worker_ as a new dependency.
-- **app.config.ts** imports `ServiceWorkerModule` and registers a service worker filename.
+- **app.config.ts** The `provideServiceWorker` provider is imported to register the service worker script.
- **index.html** has following modifications:
- A `` element that refers to _manifest.webmanifest_.
- A `` tag that sets a theme color.
@@ -342,8 +342,8 @@ Open _ngsw-config.json_ file and replace its content with this:
}
```
-In case you want to cache other static files, please refer to the [service worker configuration document](https://angular.io/guide/service-worker-config#assetgroups) on Angular.io.
+In case you want to cache other static files, please refer to the [service worker configuration document](https://angular.dev/ecosystem/service-workers/config) on Angular.dev.
### 3.2 Set Data Groups
-This part is unique to your project. We recommend being very careful about which endpoints to cache. Please refer to [service worker configuration document](https://angular.io/guide/service-worker-config#datagroups) on Angular.io for details.
+This part is unique to your project. We recommend being very careful about which endpoints to cache. Please refer to [service worker configuration document](https://angular.dev/ecosystem/service-workers/config) on Angular.dev for details.
diff --git a/docs/en/framework/ui/angular/quick-start.md b/docs/en/framework/ui/angular/quick-start.md
index f5bc88329f..0e48f0190e 100644
--- a/docs/en/framework/ui/angular/quick-start.md
+++ b/docs/en/framework/ui/angular/quick-start.md
@@ -84,10 +84,10 @@ Now let us take a look at the contents of the source folder.
- **app.config.ts** is the [root configuration](https://angular.dev/api/platform-browser/bootstrapApplication) that includes information about how parts of your application are related and what to run at the initiation of your application.
- **route.provider.ts** is used for [modifying the menu](../angular/modifying-the-menu.md).
- **assets** is for static files. A file (e.g. an image) placed in this folder will be available as is when the application is served.
-- **environments** includes one file per environment configuration. There are two configurations by default, but you may always introduce another one. These files are directly referred to in _angular.json_ and help you have different builds and application variables. Please refer to [configuring Angular application environments](https://angular.io/guide/build#configuring-application-environments) for details.
+- **environments** includes one file per environment configuration. There are two configurations by default, but you may always introduce another one. These files are directly referred to in _angular.json_ and help you have different builds and application variables. Please refer to [configuring Angular application environments](https://angular.dev/tools/cli/environments) for details.
- **index.html** is the HTML page served to visitors and will contain everything required to run your application. Servers should be configured to redirect every request to this page so that the Angular router can take over. Do not worry about how to add JavaScript and CSS files to it, because Angular CLI will do it automatically.
- **main.ts** bootstraps and configures Angular application to run in the browser. It is production-ready, so forget about it.
-- **polyfill.ts** is where you can add polyfills if you want to [support legacy browsers](https://angular.io/guide/browser-support).
+- **polyfill.ts** is where you can add polyfills if you want to [support legacy browsers](https://angular.dev/reference/versions).
- **style.scss** is the default entry point for application styles. You can change this or add new entry points in _angular.json_.
- **test.ts** helps the unit test runner discover and bootstrap spec files.
@@ -106,11 +106,11 @@ Now that you know about the files and folders, we can get the application up and
-You may modify the behavior of the **start script** (in the package.json file) by changing the parameters passed to the `ng serve` command. For instance, if you do not want a browser window to open next time you run the script, remove `--open` from the end of it. Please check [ng serve documentation](https://angular.io/cli/serve) for all available options.
+You may modify the behavior of the **start script** (in the package.json file) by changing the parameters passed to the `ng serve` command. For instance, if you do not want a browser window to open next time you run the script, remove `--open` from the end of it. Please check [ng serve documentation](https://angular.dev/cli/serve) for all available options.
### Angular Live Development Server
-The development server of Angular is based on [Webpack DevServer](https://webpack.js.org/configuration/dev-server/). It tracks changes to source files and syncs the browser window after an incremental re-compilation every time [2](#f-dev-server) you make one. Your experience will be like this:
+The development server runs via Angular's Application Builder and uses a fast, modern dev server under the hood. It tracks changes to source files and refreshes the browser after an incremental compilation every time [2](#f-dev-server) you make one. Your experience will be like this:
@@ -122,13 +122,13 @@ Please keep in mind that you should not use this server in production. To provid
1 _If you see the error above when you run the Angular app, your browser might be blocking access to the API because of the self-signed certificate. Visit that address and allow access to it (once). When you see the Swagger interface, you are good to go._ [↩](#a-certificate-error)
-2 _Sometimes, depending on the file changed, Webpack may miss the change and cannot reflect it in the browser. For example, tsconfig files are not being tracked. In such a case, please restart the development server._ [↩](#a-dev-server)
+2 _Sometimes, depending on the file changed, the development server may not pick up the change (for example, certain configuration files like tsconfig are not watched). In such a case, please restart the development server._ [↩](#a-dev-server)
---
## How to Build the Angular Application
-An Angular application can have multiple [build targets](https://angular.io/guide/glossary#target), i.e. **configurations in angular.json** which define how [Architect](https://angular.io/guide/glossary#architect) will build applications and libraries. Usually, each build configuration has a separate environment variable file. Currently, the project has two: One for development and one for production.
+An Angular application can have multiple build targets, i.e. **configurations in angular.json** which define how [Architect](https://angular.dev/reference/configs/workspace-config) will build applications and libraries. Usually, each build configuration has a separate environment variable file. Currently, the project has two: One for development and one for production.
```js
// this is what environment variables look like
@@ -161,7 +161,7 @@ export const environment = {
} as Config.Environment;
```
-When you run the development server, variables defined in _environment.ts_ take effect. Similarly, in production mode, the default environment is replaced by _environment.prod.ts_ and completely different variables become effective. You may even [create a new build configuration](https://angular.dev/reference/configs/workspace-config#alternate-build-configurations) and set [file replacements](https://angular.io/guide/build#configure-target-specific-file-replacements) to use a completely new environment. For now, we will start a production build:
+When you run the development server, variables defined in _environment.ts_ take effect. Similarly, in production mode, the default environment is replaced by _environment.prod.ts_ and completely different variables become effective. You may even [create a new build configuration](https://angular.dev/reference/configs/workspace-config#alternate-build-configurations) and set [file replacements](https://angular.dev/tools/cli/environments) to use a completely new environment. For now, we will start a production build:
1. Open your terminal and navigate to the root Angular folder.
2. Run `yarn` or `npm install` if you have not installed dependencies already.
@@ -180,18 +180,18 @@ Angular web applications run on the browser and require no server except for a [
```shell
# please replace MyProjectName with your project name
-npx servor dist/MyProjectName index.html 4200 --browse
+npx servor dist/MyProjectName/browser index.html 4200 --browse
```
This command will download and start a simple static server, a browser window at `http://localhost:4200` will open, and the compiled output of your project will be served.
Of course, you need your application to run on an optimized web server and become available to everyone. This is quite straight-forward:
-1. Create a new static web server instance. You can use a service like [Azure App Service](https://azure.microsoft.com/en-us/services/app-service/web/), [Firebase](https://firebase.google.com/docs/hosting), [Netlify](https://www.netlify.com/), [Vercel](https://vercel.com/), or even [GitHub Pages](https://angular.io/guide/deployment#deploy-to-github-pages). Another option is maintaining own web server with [NGINX](https://www.nginx.com/), [IIS](https://www.iis.net/), [Apache HTTP Server](https://httpd.apache.org/), or equivalent.
+1. Create a new static web server instance. You can use a service like [Azure App Service](https://azure.microsoft.com/en-us/services/app-service/web/), [Firebase](https://firebase.google.com/docs/hosting), [Netlify](https://www.netlify.com/), [Vercel](https://vercel.com/), or even [GitHub Pages](https://angular.dev/tools/cli/deployment). Another option is maintaining own web server with [NGINX](https://www.nginx.com/), [IIS](https://www.iis.net/), [Apache HTTP Server](https://httpd.apache.org/), or equivalent.
2. Copy the files from `dist/MyProjectName` [1](#f-dist-folder-name) to a publicly served destination on the server via CLI of the service provider, SSH, or FTP (whichever is available). This step would be defined as a job if you have a CI/CD flow.
-3. [Configure the server](https://angular.io/guide/deployment#server-configuration) to redirect all requests to the _index.html_ file. Some services do that automatically. Others require you [to add a file to the bundle via assets](https://angular.io/guide/workspace-config#assets-configuration) which describes the server how to do the redirections. Occasionally, you may need to do manual configuration.
+3. [Configure the server](https://angular.dev/tools/cli/deployment#server-configuration) to redirect all requests to the _index.html_ file. Some services do that automatically. Others require you [to add a file to the bundle via assets](https://angular.dev/reference/configs/workspace-config) which describes the server how to do the redirections. Occasionally, you may need to do manual configuration.
-In addition, you can [deploy your application to certain targets using the Angular CLI](https://angular.io/guide/deployment#automatic-deployment-with-the-cli). Here are some deploy targets:
+In addition, you can [deploy your application to certain targets using the Angular CLI](https://angular.dev/tools/cli/deployment#automatic-deployment-with-the-cli). Here are some deploy targets:
- [Azure](https://github.com/Azure/ng-deploy-azure#readme)
- [Firebase](https://github.com/angular/angularfire#readme)
diff --git a/docs/en/framework/ui/angular/router-events.md b/docs/en/framework/ui/angular/router-events.md
index b7b760ae3f..5185c9c922 100644
--- a/docs/en/framework/ui/angular/router-events.md
+++ b/docs/en/framework/ui/angular/router-events.md
@@ -7,7 +7,7 @@
# Router Events Simplified
-`RouterEvents` is a utility service for filtering specific router events and reacting to them. Please see [this page in Angular docs](https://angular.io/api/router/Event) for available router events.
+`RouterEvents` is a utility service for filtering specific router events and reacting to them. Please see [this page in Angular docs](https://angular.dev/api/router/Event) for available router events.
## Benefit
diff --git a/docs/en/framework/ui/angular/service-proxies.md b/docs/en/framework/ui/angular/service-proxies.md
index 51a6c4f5b4..c816158f77 100644
--- a/docs/en/framework/ui/angular/service-proxies.md
+++ b/docs/en/framework/ui/angular/service-proxies.md
@@ -114,7 +114,7 @@ export class BookComponent implements OnInit {
}
```
-The Angular compiler removes the services that have not been injected anywhere from the final output. See the [tree-shakable providers documentation](https://angular.io/guide/dependency-injection-providers#tree-shakable-providers).
+The Angular compiler removes the services that have not been injected anywhere from the final output. See the [tree-shakable providers documentation](https://angular.dev/guide/di/defining-dependency-providers).
### Models
@@ -152,9 +152,11 @@ export class BookComponent implements OnInit {
```
diff --git a/docs/en/framework/ui/angular/ssr-configuration.md b/docs/en/framework/ui/angular/ssr-configuration.md
new file mode 100644
index 0000000000..258fce99b4
--- /dev/null
+++ b/docs/en/framework/ui/angular/ssr-configuration.md
@@ -0,0 +1,280 @@
+```json
+//[doc-seo]
+{
+ "Description": "Learn how to configure Server-Side Rendering (SSR) for your Angular application in the ABP Framework to improve performance and SEO."
+}
+```
+
+# SSR Configuration
+
+[Server-Side Rendering (SSR)](https://angular.io/guide/ssr) is a process that involves rendering pages on the server, resulting in initial HTML content that contains the page state. This allows the browser to show the page to the user immediately, before the JavaScript bundles are downloaded and executed.
+
+SSR improves the **performance** (First Contentful Paint) and **SEO** (Search Engine Optimization) of your application.
+
+## 1. Install ABP Angular SSR
+
+The ABP Framework provides a schematic to easily add SSR support to your Angular application.
+
+Run the following command in the root folder of your Angular application:
+
+```shell
+yarn ng generate @abp/ng.schematics:ssr-add
+```
+
+Alternatively, you can specify the project name if you have a multi-project workspace:
+
+```shell
+yarn ng generate @abp/ng.schematics:ssr-add --project MyProjectName
+```
+
+This command automates the setup process by installing necessary dependencies, creating server-side entry points, and updating your configuration files.
+
+## 2. What Changes?
+
+When you run the schematic, it performs the following actions:
+
+### 2.1. Dependencies
+
+It adds the following packages to your `package.json`:
+
+- **express**: A minimal and flexible Node.js web application framework.
+- **@types/express**: Type definitions for Express.
+- **openid-client**: A library for OpenID Connect (OIDC) relying party (RP) implementation, used for authentication on the server.
+
+```json
+{
+ "dependencies": {
+ "express": "^4.18.2",
+ "openid-client": "^5.6.4"
+ },
+ "devDependencies": {
+ "@types/express": "^4.17.17"
+ }
+}
+```
+
+**For Webpack projects only:**
+- **browser-sync** (Dev dependency): Used for live reloading during development.
+
+### 2.2. Scripts & Configuration
+
+The changes depend on the builder used in your project (Application Builder or Webpack).
+
+#### Application Builder (esbuild)
+
+If your project uses the **Application Builder** (`@angular/build:application`), the schematic:
+
+- **Scripts**: Adds `serve:ssr:project-name` to serve the SSR application.
+- **angular.json**: Updates the `build` target to enable SSR (`outputMode: 'server'`) and sets the SSR entry point.
+
+```json
+{
+ "projects": {
+ "MyProjectName": {
+ "architect": {
+ "build": {
+ "options": {
+ "outputPath": "dist/MyProjectName",
+ "outputMode": "server",
+ "ssr": {
+ "entry": "src/server.ts"
+ }
+ }
+ }
+ }
+ }
+ }
+}
+```
+
+- **tsconfig**: Updates the application's `tsconfig` to include `server.ts`.
+
+#### Webpack Builder
+
+If your project uses the **Webpack Builder** (`@angular-devkit/build-angular:browser`), the schematic:
+
+- **Scripts**: Adds `dev:ssr`, `serve:ssr`, `build:ssr`, and `prerender` scripts.
+- **angular.json**: Adds new targets: `server`, `serve-ssr`, and `prerender`.
+- **tsconfig**: Updates the server's `tsconfig` to include `server.ts`.
+
+### 2.3. Files
+
+- **server.ts**: This file is the main entry point for the server-side application.
+ - **Standalone Projects**: Generates a server entry point compatible with `bootstrapApplication`.
+ - **NgModule Projects**: Generates a server entry point compatible with `platformBrowserDynamic`.
+
+```typescript
+import {
+ AngularNodeAppEngine,
+ createNodeRequestHandler,
+ isMainModule,
+ writeResponseToNodeResponse,
+} from '@angular/ssr/node';
+import express from 'express';
+import { dirname, resolve } from 'node:path';
+import { fileURLToPath } from 'node:url';
+import { environment } from './environments/environment';
+import { ServerCookieParser } from '@abp/ng.core';
+import * as oidc from 'openid-client';
+
+// ... (OIDC configuration and setup)
+
+const app = express();
+const angularApp = new AngularNodeAppEngine();
+
+// ... (OIDC routes: /authorize, /logout, /)
+
+/**
+ * Serve static files from /browser
+ */
+app.use(
+ express.static(browserDistFolder, {
+ maxAge: '1y',
+ index: false,
+ redirect: false,
+ }),
+);
+
+/**
+ * Handle all other requests by rendering the Angular application.
+ */
+app.use((req, res, next) => {
+ angularApp
+ .handle(req)
+ .then(response => {
+ if (response) {
+ res.cookie('ssr-init', 'true', {...secureCookie, httpOnly: false});
+ return writeResponseToNodeResponse(response, res);
+ } else {
+ return next()
+ }
+ })
+ .catch(next);
+});
+
+// ... (Start server logic)
+
+export const reqHandler = createNodeRequestHandler(app);
+```
+- **app.routes.server.ts**: Defines server-side routes and render modes (e.g., Prerender, Server, Client). This allows fine-grained control over how each route is rendered.
+
+```typescript
+import { RenderMode, ServerRoute } from '@angular/ssr';
+
+export const serverRoutes: ServerRoute[] = [
+ {
+ path: '**',
+ renderMode: RenderMode.Server
+ }
+];
+```
+
+- **app.config.server.ts**: Merges the application configuration with server-specific providers.
+
+```typescript
+import { mergeApplicationConfig, ApplicationConfig, provideAppInitializer, inject, PLATFORM_ID, TransferState } from '@angular/core';
+import { isPlatformServer } from '@angular/common';
+import { provideServerRendering, withRoutes } from '@angular/ssr';
+import { appConfig } from './app.config';
+import { serverRoutes } from './app.routes.server';
+import { SSR_FLAG } from '@abp/ng.core';
+
+const serverConfig: ApplicationConfig = {
+ providers: [
+ provideAppInitializer(() => {
+ const platformId = inject(PLATFORM_ID);
+ const transferState = inject(TransferState);
+ if (isPlatformServer(platformId)) {
+ transferState.set(SSR_FLAG, true);
+ }
+ }),
+ provideServerRendering(withRoutes(serverRoutes)),
+ ],
+};
+
+export const config = mergeApplicationConfig(appConfig, serverConfig);
+```
+- **index.html**: Removes the loading spinner (``) to prevent hydration mismatches.
+
+## 3. Running the Application
+
+After the installation is complete, you can run your application with SSR support.
+
+### Application Builder
+
+To serve the application with SSR in development:
+
+```shell
+yarn start
+# or
+yarn ng serve
+```
+
+To serve the built application (production):
+
+```shell
+yarn run serve:ssr:project-name
+```
+
+### Webpack Builder
+
+**Development:**
+
+```shell
+yarn run dev:ssr
+```
+
+**Production:**
+
+```shell
+yarn run build:ssr
+yarn run serve:ssr
+```
+
+## 4. Authentication & SSR
+
+The schematic installs `openid-client` to handle authentication on the server side. This ensures that when a user accesses a protected route, the server can validate their session or redirect them to the login page before rendering the content.
+
+> Ensure your OpenID Connect configuration (in `environment.ts` or `app.config.ts`) is compatible with the server environment.
+
+## 5. Deployment
+
+To deploy your Angular SSR application to a production server, follow these steps:
+
+### 5.1. Build the Application
+
+Run the build command to generate the production artifacts:
+
+```shell
+yarn build
+# or if using Webpack builder
+yarn run build:ssr
+```
+
+### 5.2. Prepare Artifacts
+
+After the build is complete, you will find the output in the `dist` folder.
+For the **Application Builder**, the output structure typically looks like this:
+
+```
+dist/MyProjectName/
+├── browser/ # Client-side bundles
+└── server/ # Server-side bundles and entry point (server.mjs)
+```
+
+You need to copy the entire `dist/MyProjectName` folder to your server.
+
+### 5.3. Run the Server
+
+On your server, navigate to the folder where you copied the artifacts and run the server using Node.js:
+
+```shell
+node server/server.mjs
+```
+
+> [!TIP]
+> It is recommended to use a process manager like [PM2](https://pm2.keymetrics.io/) to keep your application alive and handle restarts.
+
+```shell
+pm2 start server/server.mjs --name "my-app"
+```
diff --git a/docs/en/framework/ui/angular/subscription-service.md b/docs/en/framework/ui/angular/subscription-service.md
index b04a3dbf58..c64edb9fe0 100644
--- a/docs/en/framework/ui/angular/subscription-service.md
+++ b/docs/en/framework/ui/angular/subscription-service.md
@@ -7,7 +7,7 @@
# Managing RxJS Subscriptions
-`SubscriptionService` is a utility service to provide an easy unsubscription from RxJS observables in Angular components and directives. Please see [why you should unsubscribe from observables on instance destruction](https://angular.io/guide/lifecycle-hooks#cleaning-up-on-instance-destruction).
+`SubscriptionService` is a utility service to provide an easy unsubscription from RxJS observables in Angular components and directives. Please see [why you should unsubscribe from observables on instance destruction](https://angular.dev/guide/components/lifecycle).
## Getting Started
diff --git a/docs/en/framework/ui/angular/testing.md b/docs/en/framework/ui/angular/testing.md
index c0d5ff312c..ab215f7eba 100644
--- a/docs/en/framework/ui/angular/testing.md
+++ b/docs/en/framework/ui/angular/testing.md
@@ -7,7 +7,7 @@
# Unit Testing Angular UI
-ABP Angular UI is tested like any other Angular application. So, [the guide here](https://angular.io/guide/testing) applies to ABP too. That said, we would like to point out some **unit testing topics specific to ABP Angular applications**.
+ABP Angular UI is tested like any other Angular application. So, [the guide here](https://angular.dev/guide/testing) applies to ABP too. That said, we would like to point out some **unit testing topics specific to ABP Angular applications**.
## Setup
diff --git a/docs/en/framework/ui/angular/theming.md b/docs/en/framework/ui/angular/theming.md
index cb6f8fe8b0..1351a02f33 100644
--- a/docs/en/framework/ui/angular/theming.md
+++ b/docs/en/framework/ui/angular/theming.md
@@ -81,8 +81,8 @@ You can run the following command in **Angular** project directory to copy the s
### Global/Component Styles
-Angular can bundle global style files and component styles with components.
-See the [component styles](https://angular.io/guide/component-styles) guide on Angular documentation for more information.
+Angular can bundle global style files and component styles with components.
+See the [component styles](https://angular.dev/guide/components/styling) guide on Angular documentation for more information.
### Layout Parts
@@ -238,8 +238,10 @@ import { Router } from '@angular/router';
selector: 'abp-current-user-test',
template: `
-
+ @if (data.textTemplate.icon){
+
{%{{{ data.textTemplate.text | abpLocalization }}}%}
+ }
`,
})
diff --git a/docs/en/framework/ui/angular/track-by-service.md b/docs/en/framework/ui/angular/track-by-service.md
index 046935e5b6..15cdd9577f 100644
--- a/docs/en/framework/ui/angular/track-by-service.md
+++ b/docs/en/framework/ui/angular/track-by-service.md
@@ -5,9 +5,9 @@
}
```
-# Easy *ngFor trackBy
+# Easy @for() track
-`TrackByService` is a utility service to provide an easy implementation for one of the most frequent needs in Angular templates: `TrackByFunction`. Please see [this page in Angular docs](https://angular.io/guide/template-syntax#ngfor-with-trackby) for its purpose.
+`TrackByService` is a utility service to provide an easy implementation for one of the most frequent needs in Angular templates: `TrackByFunction`. Please see [this page in Angular docs](https://angular.dev/guide/templates/control-flow) for its purpose.
@@ -54,8 +54,9 @@ You can use `by` to get a `TrackByFunction` that tracks the iterated object base
```html
-
-
+ }
`,
})
class DemoComponent {
diff --git a/docs/en/get-started/empty-aspnet-core-application.md b/docs/en/get-started/empty-aspnet-core-application.md
index 78eb744eda..5bcec4ebb6 100644
--- a/docs/en/get-started/empty-aspnet-core-application.md
+++ b/docs/en/get-started/empty-aspnet-core-application.md
@@ -11,7 +11,7 @@ This tutorial explains how to start ABP from scratch with minimal dependencies.
## Create a New Project
-1. Create a new AspNet Core Web Application with Visual Studio 2022 (17.0.0+):
+1. Create a new AspNet Core Web Application with Visual Studio 2026 (18.0.0+):

diff --git a/docs/en/get-started/layered-web-application.md b/docs/en/get-started/layered-web-application.md
index dc65e45829..b2bd05454a 100644
--- a/docs/en/get-started/layered-web-application.md
+++ b/docs/en/get-started/layered-web-application.md
@@ -22,8 +22,8 @@ In this quick start guide, you will learn how to create and run a layered (and p
First things first! Let's setup your development environment before creating the first project. The following tools should be installed on your development machine:
-* [Visual Studio 2022](https://visualstudio.microsoft.com/) or another IDE that supports [.NET 9.0+](https://dotnet.microsoft.com/download/dotnet) development.
-* [.NET 9.0+](https://dotnet.microsoft.com/en-us/download/dotnet){{ if UI != "Blazor" }}
+* [Visual Studio 2026](https://visualstudio.microsoft.com/) or another IDE that supports [.NET 10.0+](https://dotnet.microsoft.com/download/dotnet) development.
+* [.NET 10.0+](https://dotnet.microsoft.com/en-us/download/dotnet){{ if UI != "Blazor" }}
* [Node v22.11+](https://nodejs.org/){{ end }}{{ if UI == "NG" }}
* [Yarn v1.22+ (not v2+)](https://classic.yarnpkg.com/en/docs/install) or npm v10+ (already installed with Node){{ end }}
* [Docker Desktop](https://www.docker.com/products/docker-desktop/)
@@ -276,4 +276,9 @@ You can start the following application(s):
> For example in non-tiered MVC with public website application:
-
\ No newline at end of file
+
+
+## What's next?
+
+- [TODO Application Tutorial with Layered Solution](../tutorials/todo/layered/index.md)
+- [Web Application Development Tutorial](../tutorials/book-store/index.md)
\ No newline at end of file
diff --git a/docs/en/get-started/microservice.md b/docs/en/get-started/microservice.md
index fb8626baef..d57c652b8e 100644
--- a/docs/en/get-started/microservice.md
+++ b/docs/en/get-started/microservice.md
@@ -15,8 +15,8 @@ In this quick start guide, you will learn how to create and run a microservice s
First things first! Let's setup your development environment before creating the first project. The following tools should be installed on your development machine:
-* [Visual Studio 2022](https://visualstudio.microsoft.com/vs/) or another IDE that supports .NET development
-* [.NET 9.0+](https://dotnet.microsoft.com/en-us/download/dotnet)
+* [Visual Studio 2026](https://visualstudio.microsoft.com/vs/) or another IDE that supports .NET development
+* [.NET 10.0+](https://dotnet.microsoft.com/en-us/download/dotnet)
* [Node v22.11+](https://nodejs.org/)
* [Yarn v1.22+ (not v2+)](https://classic.yarnpkg.com/en/docs/install) or npm v10+ (already installed with Node), **This is required for the Angular applications.**
* [Docker Desktop (with Kubernetes enabled)](https://www.docker.com/products/docker-desktop/)
diff --git a/docs/en/get-started/pre-requirements.md b/docs/en/get-started/pre-requirements.md
index 8d3555fb99..8aad4818ab 100644
--- a/docs/en/get-started/pre-requirements.md
+++ b/docs/en/get-started/pre-requirements.md
@@ -108,9 +108,11 @@ If you are using Helm, you can install NGINX Ingress using the following command
```cs
helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx
helm repo update
-helm upgrade --install --version=4.0.19 ingress-nginx ingress-nginx/ingress-nginx
+helm upgrade --install --version=4.0.19 ingress-nginx ingress-nginx/ingress-nginx --set controller.config.enable-underscores-in-headers="true"
```
+> [enable-underscores-in-headers](https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/configmap/#enable-underscores-in-headers) is required to allow http request use `__tenant` to pass tenant information to the backend service.
+
### mkcert
Use mkcert to generate trusted certificates for local development. You can install mkcert by following the [official mkcert installation guide](https://github.com/FiloSottile/mkcert#installation).
diff --git a/docs/en/get-started/single-layer-web-application.md b/docs/en/get-started/single-layer-web-application.md
index 06c5ed90f9..9ee87fd439 100644
--- a/docs/en/get-started/single-layer-web-application.md
+++ b/docs/en/get-started/single-layer-web-application.md
@@ -21,8 +21,8 @@ In this quick start guide, you will learn how to create and run a single layer w
First things first! Let's setup your development environment before creating the first project. The following tools should be installed on your development machine:
-* [Visual Studio 2022](https://visualstudio.microsoft.com/) or another IDE that supports [.NET 9.0+](https://dotnet.microsoft.com/download/dotnet) development.
-* [.NET 9.0+](https://dotnet.microsoft.com/en-us/download/dotnet){{ if UI != "Blazor" }}
+* [Visual Studio 2026](https://visualstudio.microsoft.com/) or another IDE that supports [.NET 10.0+](https://dotnet.microsoft.com/download/dotnet) development.
+* [.NET 10.0+](https://dotnet.microsoft.com/en-us/download/dotnet){{ if UI != "Blazor" }}
* [Node v22.11+](https://nodejs.org/){{ end }}{{ if UI == "NG" }}
* [Yarn v1.22+ (not v2+)](https://classic.yarnpkg.com/en/docs/install) or npm v10+ (already installed with Node){{ end }}
@@ -185,3 +185,7 @@ You can then hit *F5* or *Ctrl + F5* to run the web application. It will run and

You can use `admin` as username and `1q2w3E*` as default password to login to the application.
+
+## What's next?
+
+- [TODO Application Tutorial with Single-Layer Solution](../tutorials/todo/single-layer/index.md)
\ No newline at end of file
diff --git a/docs/en/images/abp-overall-diagram-1600.png b/docs/en/images/abp-overall-diagram-1600.png
index 16d397466a..3b02dd66dc 100644
Binary files a/docs/en/images/abp-overall-diagram-1600.png and b/docs/en/images/abp-overall-diagram-1600.png differ
diff --git a/docs/en/images/db-options.png b/docs/en/images/db-options.png
index 91d2b51ce7..d25811c49b 100644
Binary files a/docs/en/images/db-options.png and b/docs/en/images/db-options.png differ
diff --git a/docs/en/images/elsa-studio-wasm.png b/docs/en/images/elsa-studio-wasm.png
new file mode 100644
index 0000000000..9365ef6a4c
Binary files /dev/null and b/docs/en/images/elsa-studio-wasm.png differ
diff --git a/docs/en/images/ui-options.png b/docs/en/images/ui-options.png
index 6affab9d21..3c30cd16d7 100644
Binary files a/docs/en/images/ui-options.png and b/docs/en/images/ui-options.png differ
diff --git a/docs/en/modules/account-pro.md b/docs/en/modules/account-pro.md
index 62d7a00785..81e1177e33 100644
--- a/docs/en/modules/account-pro.md
+++ b/docs/en/modules/account-pro.md
@@ -7,7 +7,7 @@
# Account Module (Pro)
-> You must have an ABP Team or a higher license to use this module.
+> You must have an [ABP Team or a higher license](https://abp.io/pricing) to use this module.
This module implements the Login, Register, Forgot Password, Email Confirmation, Password Reset, sending and confirming Two-Factor Authentication, user lockout, switch between tenants functionalities of an application;
diff --git a/docs/en/modules/ai-management/index.md b/docs/en/modules/ai-management/index.md
index b85112efb7..a126d9c59d 100644
--- a/docs/en/modules/ai-management/index.md
+++ b/docs/en/modules/ai-management/index.md
@@ -1,9 +1,19 @@
+```json
+//[doc-seo]
+{
+ "Description": "Discover how to implement AI management in your ABP Framework application, enhancing workspace dynamics with easy installation options."
+}
+```
+
# AI Management (Pro)
> You must have an ABP Team or a higher license to use this module.
-This module implements AI (Artificial Intelligence) management capabilities on top of the [Artificial Intelligence Workspaces](../../framework/infrastructure/artificial-intelligence.md) feature of the ABP Framework and allows to manage workspaces dynamically from the application including UI components and API endpoints.
+> **⚠️ Important Notice**
+> The **AI Management Module** is currently in **preview** and not yet production-ready. The documentation and implementation are subject to change.
+> We recommend using this module for **evaluation and experimentation** only, not in production environments for now.
+This module implements AI (Artificial Intelligence) management capabilities on top of the [Artificial Intelligence Workspaces](../../framework/infrastructure/artificial-intelligence/index.md) feature of the ABP Framework and allows to manage workspaces dynamically from the application including UI components and API endpoints.
## How to Install
@@ -32,10 +42,10 @@ AI Management module packages are designed for various usage scenarios. Packages
### Menu Items
-AI Management module adds the following items to the "Main" menu, under the "Administration" menu item:
+AI Management module adds the following items to the "Main" menu:
-* **Workspaces**: Workspace management page.
-* **Chat**: AI chat interface for testing workspaces.
+* **AI Management**: Root menu item for AI Management module. (`AIManagement`)
+ * **Workspaces**: Workspace management page. (`AIManagement.Workspaces`)
`AIManagementMenus` class has the constants for the menu item names.
@@ -68,7 +78,7 @@ The AI Management module includes a built-in chat interface for testing workspac
* Test streaming responses
* Verify workspace configuration before using in production
-> Access the chat interface at: `/AIManagement/Chat`
+> Access the chat interface at: `/AIManagement/Workspaces/{WorkspaceName}`
## Workspace Configuration
@@ -135,14 +145,15 @@ PreConfigure(options =>
Example (data seeding):
```csharp
-await _workspaceRepository.InsertAsync(new Workspace(
+var workspace = new Workspace(
name: "CustomerSupportWorkspace",
provider: "OpenAI",
modelName: "gpt-4",
- apiKey: "your-api-key",
- systemPrompt: "You are a helpful customer support assistant.",
- requiredPermissionName: "MyApp.CustomerSupport"
-));
+ apiKey: "your-api-key"
+);
+workspace.ApplicationName = ApplicationInfoAccessor.ApplicationName;
+workspace.SystemPrompt = "You are a helpful customer support assistant.";
+await _workspaceRepository.InsertAsync(workspace);
```
### Workspace Naming Rules
@@ -155,8 +166,6 @@ await _workspaceRepository.InsertAsync(new Workspace(
The AI Management module defines the following permissions:
-### Workspace Management Permissions
-
| Permission | Description | Default Granted To |
|------------|-------------|-------------------|
| `AIManagement.Workspaces` | View workspaces | Admin role |
@@ -164,11 +173,6 @@ The AI Management module defines the following permissions:
| `AIManagement.Workspaces.Update` | Edit existing workspaces | Admin role |
| `AIManagement.Workspaces.Delete` | Delete workspaces | Admin role |
-### Chat Permissions
-
-| Permission | Description | Default Granted To |
-|------------|-------------|-------------------|
-| `AIManagement.Chat` | Access chat interface | Admin role |
### Workspace-Level Permissions
@@ -184,9 +188,8 @@ var workspace = new Workspace(
```
When a workspace has a required permission:
-* Only users with that permission can access the workspace
+* Only authorized users with that permission can access the workspace endpoints
* Users without the permission will receive an authorization error
-* The workspace will not appear in the workspace selection dropdown for unauthorized users
## Usage Scenarios
@@ -248,7 +251,7 @@ public class MyService
}
```
-> See [Artificial Intelligence](../../framework/infrastructure/artificial-intelligence.md) documentation for more details about workspace configuration.
+> See [Artificial Intelligence](../../framework/infrastructure/artificial-intelligence/index.md) documentation for more details about workspace configuration.
### Scenario 2: AI Management with Domain Layer Dependency (Local Execution)
@@ -626,6 +629,6 @@ The cache is automatically invalidated when workspaces are created, updated, or
## See Also
-- [Artificial Intelligence Infrastructure](../../framework/infrastructure/artificial-intelligence.md): Learn about the underlying AI workspace infrastructure
+- [Artificial Intelligence Infrastructure](../../framework/infrastructure/artificial-intelligence/index.md): Learn about the underlying AI workspace infrastructure
- [Microsoft.Extensions.AI](https://learn.microsoft.com/en-us/dotnet/ai/): Microsoft's unified AI abstractions
-- [Semantic Kernel](https://learn.microsoft.com/en-us/semantic-kernel/): Microsoft's Semantic Kernel integration
\ No newline at end of file
+- [Semantic Kernel](https://learn.microsoft.com/en-us/semantic-kernel/): Microsoft's Semantic Kernel integration
diff --git a/docs/en/modules/audit-logging-pro.md b/docs/en/modules/audit-logging-pro.md
index 20f220857c..e64b39dc66 100644
--- a/docs/en/modules/audit-logging-pro.md
+++ b/docs/en/modules/audit-logging-pro.md
@@ -7,7 +7,7 @@
# Audit Logging Module (Pro)
-> You must have an ABP Team or a higher license to use this module.
+> You must have an [ABP Team or a higher license](https://abp.io/pricing) to use this module.
This module implements the Audit Logging system of an application;
diff --git a/docs/en/modules/chat.md b/docs/en/modules/chat.md
index b6932149fb..fa87a8eef6 100644
--- a/docs/en/modules/chat.md
+++ b/docs/en/modules/chat.md
@@ -7,7 +7,7 @@
# Chat Module (Pro)
-> You must have an ABP Team or a higher license to use this module.
+> You must have an [ABP Team or a higher license](https://abp.io/pricing) to use this module.
This module implements real time messaging between users for an application.
diff --git a/docs/en/modules/cms-kit-pro/contact-form.md b/docs/en/modules/cms-kit-pro/contact-form.md
index 6cdb08a569..eafa4b80b3 100644
--- a/docs/en/modules/cms-kit-pro/contact-form.md
+++ b/docs/en/modules/cms-kit-pro/contact-form.md
@@ -7,7 +7,7 @@
# CMS Kit Pro: Contact Management
-> You must have an ABP Team or a higher license to use CMS Kit Pro module's features.
+> You must have an [ABP Team or a higher license](https://abp.io/pricing) to use CMS Kit Pro module's features.
CMS Kit provides a widget to create a contact form on your website.
diff --git a/docs/en/modules/cms-kit-pro/faq.md b/docs/en/modules/cms-kit-pro/faq.md
index 78ec252d17..23d90d9705 100644
--- a/docs/en/modules/cms-kit-pro/faq.md
+++ b/docs/en/modules/cms-kit-pro/faq.md
@@ -7,7 +7,7 @@
# CMS Kit Pro: FAQ System
-> You must have an ABP Team or a higher license to use CMS Kit Pro module's features.
+> You must have an [ABP Team or a higher license](https://abp.io/pricing) to use CMS Kit Pro module's features.
The CMS kit provides a **FAQ** system to allow users to create, edit and delete FAQ's. Here is a screenshot of the FAQ widget:
diff --git a/docs/en/modules/cms-kit-pro/index.md b/docs/en/modules/cms-kit-pro/index.md
index 8a29db2d63..b7ce2f03d4 100644
--- a/docs/en/modules/cms-kit-pro/index.md
+++ b/docs/en/modules/cms-kit-pro/index.md
@@ -7,7 +7,7 @@
# CMS Kit Module (Pro)
-> You must have an ABP Team or a higher license to use this module.
+> You must have an [ABP Team or a higher license](https://abp.io/pricing) to use this module.
This module extends the [open-source CMS Kit module](../cms-kit) and adds additional CMS (Content Management System) capabilities to your application.
diff --git a/docs/en/modules/cms-kit-pro/newsletter.md b/docs/en/modules/cms-kit-pro/newsletter.md
index 84cc2ee34c..3097011658 100644
--- a/docs/en/modules/cms-kit-pro/newsletter.md
+++ b/docs/en/modules/cms-kit-pro/newsletter.md
@@ -7,7 +7,7 @@
# CMS Kit Pro: Newsletter System
-> You must have an ABP Team or a higher license to use CMS Kit Pro module's features.
+> You must have an [ABP Team or a higher license](https://abp.io/pricing) to use CMS Kit Pro module's features.
CMS Kit provides a **newsletter** system to allow users to subscribe to newsletters. Here a screenshot of the newsletter subscription widget:
diff --git a/docs/en/modules/cms-kit-pro/page-feedback.md b/docs/en/modules/cms-kit-pro/page-feedback.md
index ac2278d893..559ed98a3a 100644
--- a/docs/en/modules/cms-kit-pro/page-feedback.md
+++ b/docs/en/modules/cms-kit-pro/page-feedback.md
@@ -7,7 +7,7 @@
# CMS Kit Pro: Page Feedback System
-> You must have an ABP Team or a higher license to use CMS Kit Pro module's features.
+> You must have an [ABP Team or a higher license](https://abp.io/pricing) to use CMS Kit Pro module's features.
The CMS Kit Pro module provides a comprehensive **Page Feedback** system that enables you to collect valuable user feedback about your website pages. This system allows visitors to quickly rate their experience and provide comments, helping you understand user satisfaction and identify areas for improvement.
diff --git a/docs/en/modules/cms-kit-pro/poll.md b/docs/en/modules/cms-kit-pro/poll.md
index f10baf080e..dfee545219 100644
--- a/docs/en/modules/cms-kit-pro/poll.md
+++ b/docs/en/modules/cms-kit-pro/poll.md
@@ -7,7 +7,7 @@
# CMS Kit Pro: Poll System
-> You must have an ABP Team or a higher license to use CMS Kit Pro module's features.
+> You must have an [ABP Team or a higher license](https://abp.io/pricing) to use CMS Kit Pro module's features.
CMS Kit provides a **poll** system to allow users to create, edit and delete polls. Here is a screenshot of the poll widget:
diff --git a/docs/en/modules/cms-kit-pro/url-forwarding.md b/docs/en/modules/cms-kit-pro/url-forwarding.md
index cd164ebba0..2a1b639cab 100644
--- a/docs/en/modules/cms-kit-pro/url-forwarding.md
+++ b/docs/en/modules/cms-kit-pro/url-forwarding.md
@@ -7,7 +7,7 @@
# CMS Kit Pro: URL Forwarding System
-> You must have an ABP Team or a higher license to use CMS Kit Pro module's features.
+> You must have an [ABP Team or a higher license](https://abp.io/pricing) to use CMS Kit Pro module's features.
CMS Kit provides a **URL forwarding** system to create URLs that redirect to other pages or external websites.
diff --git a/docs/en/modules/cms-kit/dynamic-widget.md b/docs/en/modules/cms-kit/dynamic-widget.md
index 8644f7cd63..f0646cc00f 100644
--- a/docs/en/modules/cms-kit/dynamic-widget.md
+++ b/docs/en/modules/cms-kit/dynamic-widget.md
@@ -124,21 +124,26 @@ In this image, after choosing your widget (on the other case, it changes automat
You can edit this output manually if do any wrong coding for that (wrong value or typo) you won't see the widget, even so, your page will be viewed successfully.
-## Options
-To configure the widget, you should define the below code in YourModule.cs
+## Options
+
+To add content widgets, you should configure the `CmsKitContentWidgetOptions` in your module's `ConfigureServices` method:
```csharp
Configure(options =>
{
options.AddWidget(widgetType: "Today", widgetName: "CmsToday", parameterWidgetName: "Format");
+
+ // Alternatively, you can add a widget conditionally based on a global feature being enabled
+ options.AddWidgetIfFeatureEnabled(typeof(PagesFeature), "Today", "CmsToday", "Format");
});
```
-Let's look at these parameters in detail
-* `widgetType` is used for end-user and more readable names. The following bold word represents widgetType.
-[Widget Type="**Today**" Format="yyyy-dd-mm HH:mm:ss"].
+The `CmsKitContentWidgetOptions` provides two methods for registering widgets:
-* `widgetName` is used for your widget name used in code for the name of the `ViewComponent`.
+- **AddWidget:** Registers a widget that will be available in the content editor. It accepts the following parameters:
+ - `widgetType` (required): A user-friendly name for the widget that appears in the widget selection dropdown and is used in content markup. For example, in `[Widget Type="Today"]`, `"Today"` is the `widgetType`.
+ - `widgetName` (required): The name of the `ViewComponent` that will be rendered. This must match the `Name` attribute of your `ViewComponent` (e.g., `[ViewComponent(Name = "CmsToday")]`).
+ - `parameterWidgetName` (optional): The name of the parameter widget that will be displayed in the "Add Widget" modal to collect parameter values from users. This is only required when your widget needs parameters.
-* `parameterWidgetName` is used the for editor component side to see on the `Add Widget` modal.
-After choosing the widget type from listbox (now just defined `Format`) and renders this widget automatically. It's required only to see UI once using parameters
\ No newline at end of file
+- **AddWidgetIfFeatureEnabled:** Registers a widget conditionally, only if a specified [global feature](../../framework/infrastructure/global-features.md) is enabled. It accepts the same parameters as `AddWidget`, plus an additional first parameter:
+ - `featureType` (required): The type of the global feature that must be enabled for the widget to be available (e.g., `typeof(PagesFeature)`).
\ No newline at end of file
diff --git a/docs/en/modules/elsa-pro.md b/docs/en/modules/elsa-pro.md
index 3a6ec4533b..6b93e42368 100644
--- a/docs/en/modules/elsa-pro.md
+++ b/docs/en/modules/elsa-pro.md
@@ -1,10 +1,17 @@
+```json
+//[doc-seo]
+{
+ "Description": "Integrate Elsa Workflows into your ABP applications with this Pro module. Learn installation and setup for seamless workflow management."
+}
+```
+
# Elsa Module (Pro)
> You must have an ABP Team or a higher license to use this module.
This module integrates [Elsa Workflows](https://docs.elsaworkflows.io/) into ABP Framework applications and is designed to make it easy for developers to use Elsa's capabilities within their ABP-based projects. For creating, managing, and customizing workflows themselves, please refer to [the official Elsa documentation](https://docs.elsaworkflows.io/).
-## How to install
+## How to Install
The Elsa module is not installed in [the startup templates](../solution-templates/layered-web-application) by default and must be installed manually. There are two ways of installing a module into your application and each one of these approaches is explained in the next sections.
@@ -37,6 +44,23 @@ After adding the package references, open the module class of the project (e.g.:
> If you are using Blazor Web App, you need to add the `Volo.Elsa.Admin.Blazor.WebAssembly` package to the **{ProjectName}.Blazor.Client.csproj** project and add the `Volo.Elsa.Admin.Blazor.Server` package to the **{ProjectName}.Blazor.csproj** project.
+### `AbpElsaAspNetCoreModule` and `AbpElsaIdentityModule`
+
+These two modules generally will be added to your authentication project. Please add `Volo.Elsa.Abp.AspNetCore` and `Volo.Elsa.Abp.Identity` packages to your project and add the `AbpElsaAspNetCoreModule` and `AbpElsaIdentityModule` to the `DependsOn` attribute of your module class based on your project structure:
+
+```xml
+
+
+```
+
+```csharp
+[DependsOn(
+ //...
+ typeof(AbpElsaAspNetCoreModule),
+ typeof(AbpElsaIdentityModule)
+)]
+```
+
## The Elsa Module
The Elsa Workflows has its own database provider, and also has a Tenant/Role/User system. They are under active development, so the ABP Elsa module is not yet fully integrated. Below is the current status of each module in the ABP's Elsa Module:
@@ -56,6 +80,49 @@ The rest of the projects/modules are basically empty and will be implemented in
- `AbpElsaBlazorWebAssemblyModule(Volo.Elsa.Abp.Blazor.WebAssembly)`
- `AbpElsaWebModule(Volo.Elsa.Abp.Web)`
+## Configure the Elsa Server
+
+You need to configure Elsa in your ABP application to use its features. You can do that in the `ConfigureServices` method of your `YourElsaAppModule` class as shown below:
+
+> For more information about configuring Elsa, please refer to [the official Elsa documentation](https://docs.elsaworkflows.io/).
+
+```cs
+private void ConfigureElsa(ServiceConfigurationContext context, IConfiguration configuration)
+{
+ var connectionString = configuration.GetConnectionString("Default")!;
+ context.Services
+ .AddElsa(elsa => elsa
+ .UseAbpIdentity(identity => // Use UseAbpIdentity instead of UseIdentity to integrate with ABP Identity module
+ {
+ identity.TokenOptions = options => options.SigningKey = "large-signing-key-for-signing-JWT-tokens";
+ })
+ .UseWorkflowManagement(management => management.UseEntityFrameworkCore(ef => ef.UseSqlServer(connectionString)))
+ .UseWorkflowRuntime(runtime => runtime.UseEntityFrameworkCore(ef => ef.UseSqlServer(connectionString)))
+ .UseScheduling()
+ .UseJavaScript()
+ .UseLiquid()
+ .UseCSharp()
+ .UseHttp(http => http.ConfigureHttpOptions = options => configuration.GetSection("Http").Bind(options))
+ .UseWorkflowsApi()
+ .AddActivitiesFrom()
+ .AddWorkflowsFrom()
+ );
+}
+```
+
+## Elsa Database Migration
+
+Elsa module uses its own database context and migration system, ABP Elsa module doesn't contain any `aggregate root/entity` at the moment. So, **you don't need to create any initial migration for Elsa module**. You just need to configure the Elsa Services as follows:
+
+```cs
+.UseWorkflowManagement(management => management.UseEntityFrameworkCore(ef => ef.UseSqlServer(connectionString)))
+.UseWorkflowRuntime(runtime => runtime.UseEntityFrameworkCore(ef => ef.UseSqlServer(connectionString)))
+```
+
+When you run your application, Elsa will create its own database tables if they do not exist.
+
+> See [how to configure Elsa Workflows to use different database providers for persistence, including SQL Server, PostgreSQL, and MongoDB](https://docs.elsaworkflows.io/getting-started/database-configuration) for more information.
+
### Elsa Module Permissions
The Elsa Workflow API endpoints check permissions. Also, it has a `*` wildcard permission to allow all permissions.
@@ -72,14 +139,24 @@ You can also grant parts of the permissions to a role or user. It will add the `
### Elsa Studio
-Elsa Studio is an **independent** web application that allows you to design, manage, and execute workflows. It is built using **Blazor Server/WebAssembly**.
+[Elsa Studio](https://docs.elsaworkflows.io/application-types/elsa-studio) is a **standalone** web application that allows you to design, manage, and execute workflows. It is built using **Blazor Server/WebAssembly**.
+
+`ElsaDemoApp.Studio.WASM` is a sample Blazor WebAssembly project that demonstrates how to use Elsa Studio with ELSA Server with ABP Framework.
+
+> Elsa Studio has its own layout and theme, and you can't integrate it into an ABP Blazor project for now.
+
+
+
+Please check the [Elsa Workflows - Sample Workflow Demo](../samples/elsa-workflows-demo.md) document to download its source code for review.
+
+#### Elsa Studio Authentication
Elsa Studio requires authentication and there are two ways to authenticate Elsa Studio:
* Password Flow Authentication
* Code Flow Authentication
-#### Elsa Studio - Password Flow Authentication
+##### Elsa Studio - Password Flow Authentication
The `AbpElsaIdentityModule(Volo.Elsa.Abp.Identity)` module is used to integrate with [ABP Identity module](./identity-pro.md) to check Elsa Studio *username* and *password* against ABP Identity.
@@ -109,7 +186,7 @@ Once, you logged in to the application, you can start defining workflows, manage

-#### Elsa Studio - Code Flow Authentication
+##### Elsa Studio - Code Flow Authentication
ABP applications use [OpenIddict](./openiddict-pro.md) for authentication. So, you can use the [Authorization Code Flow](https://oauth.net/2/grant-types/authorization-code/) to authenticate Elsa Studio.
diff --git a/docs/en/modules/file-management.md b/docs/en/modules/file-management.md
index 5725af4297..8a5f7aae29 100644
--- a/docs/en/modules/file-management.md
+++ b/docs/en/modules/file-management.md
@@ -7,7 +7,7 @@
# File Management Module (Pro)
-> You must have an ABP Team or a higher license to use this module.
+> You must have an [ABP Team or a higher license](https://abp.io/pricing) to use this module.
This module is used to upload, download and organize files in a hierarchical folder structure. It is also compatible to multi-tenancy and you can determine total size limit for your tenants.
@@ -144,6 +144,12 @@ You can move files by clicking `Actions -> Move` on the table.
You can rename a file by clicking `Actions -> Rename` on the table.
+###### File Sharing
+
+To share a file, click `Actions -> Share` in the table. Once sharing is enabled, you can copy the shared link directly from the table.
+
+> Anyone with the shared link will be able to access the file while sharing is enabled.
+
## Data Seed
This module doesn't seed any data.
diff --git a/docs/en/modules/forms.md b/docs/en/modules/forms.md
index f903cc471b..f2456b792b 100644
--- a/docs/en/modules/forms.md
+++ b/docs/en/modules/forms.md
@@ -7,7 +7,7 @@
# Forms Module (Pro)
-> You must have an ABP Team or a higher license to use this module.
+> You must have an [ABP Team or a higher license](https://abp.io/pricing) to use this module.
This module allows you to create questionnaires to gather information. The forms module can store responses as they come in and you can export the data to a CSV file. You can share your form with others with your form unique link. You can request authentication or allow anonymous reply. It is similar to the Google Form application. Usage area is quite wide, you can create surveys, manage event registrations, collect email addresses for a newsletter, create a quiz, and even receive an order request.
diff --git a/docs/en/modules/gdpr.md b/docs/en/modules/gdpr.md
index f797a3b713..0a0bd7fb09 100644
--- a/docs/en/modules/gdpr.md
+++ b/docs/en/modules/gdpr.md
@@ -7,7 +7,7 @@
# GDPR Module (Pro)
-> You must have an ABP Team or a higher license to use this module.
+> You must have an [ABP Team or a higher license](https://abp.io/pricing) to use this module.
This module allows users to download and delete their personal data collected by the application.
diff --git a/docs/en/modules/identity-pro.md b/docs/en/modules/identity-pro.md
index f23b9e801a..0d26154932 100644
--- a/docs/en/modules/identity-pro.md
+++ b/docs/en/modules/identity-pro.md
@@ -7,7 +7,7 @@
# Identity Module (Pro)
-> You must have an ABP Team or a higher license to use this module.
+> You must have an [ABP Team or a higher license](https://abp.io/pricing) to use this module.
This module implements the User and Role system of an application;
@@ -434,9 +434,10 @@ This module doesn't define any additional distributed event. See the [standard d
## See Also
* [Import External Users](./identity/import-external-users.md)
-* [LDAP Login](./identity/idap.md)
+* [LDAP Login](./identity/ldap.md)
* [OAuth Login](./identity/oauth-login.md)
* [Periodic Password Change (Password Aging)](./identity/periodic-password-change.md)
* [Two Factor Authentication](./identity/two-factor-authentication.md)
* [Session Management](./identity/session-management.md)
* [Password History](./identity/password-history.md)
+
diff --git a/docs/en/modules/identity-server-pro.md b/docs/en/modules/identity-server-pro.md
index 66e16fcb71..48ead33082 100644
--- a/docs/en/modules/identity-server-pro.md
+++ b/docs/en/modules/identity-server-pro.md
@@ -7,7 +7,7 @@
# Identity Server Module (Pro)
-> You must have an ABP Team or a higher license to use this module.
+> You must have an [ABP Team or a higher license](https://abp.io/pricing) to use this module.
This module provides integration and management functionality for Identity Server;
diff --git a/docs/en/modules/identity/import-external-users.md b/docs/en/modules/identity/import-external-users.md
index 562515ceee..00c8e4b824 100644
--- a/docs/en/modules/identity/import-external-users.md
+++ b/docs/en/modules/identity/import-external-users.md
@@ -9,7 +9,7 @@
## Introduction
-> You must have an ABP Team or a higher license to use this module & its features.
+> You must have an [ABP Team or a higher license](https://abp.io/pricing) to use this module & its features.
The Identity PRO module has built-in `LdapExternalLoginProvider` and `OAuthExternalLoginProvider` services. They not only support external login but also import users.
diff --git a/docs/en/modules/identity/idap.md b/docs/en/modules/identity/ldap.md
similarity index 95%
rename from docs/en/modules/identity/idap.md
rename to docs/en/modules/identity/ldap.md
index cf4c8fbcaa..c01bc630ef 100644
--- a/docs/en/modules/identity/idap.md
+++ b/docs/en/modules/identity/ldap.md
@@ -9,13 +9,13 @@
## Introduction
-> You must have an ABP Team or a higher license to use this module & its features.
+> You must have an [ABP Team or a higher license](https://abp.io/pricing) to use this module & its features.
The Identity PRO module has built-in `LdapExternalLoginProvider` and `OpenLdapManager` services. It implements LDAP authentication and gets user info for [external login](https://github.com/abpframework/abp/issues/4977).
The cross-platform [LdapForNet](https://www.nuget.org/packages/LdapForNet/) library is used for Windows LDAP authentication. See [LdapForNet GitHub repository](https://github.com/flamencist/ldap4net) for more information.
-> You must have an ABP Team or a higher license to use this module & its features.
+> You must have an [ABP Team or a higher license](https://abp.io/pricing) to use this module & its features.
## How to enable LDAP external login?
diff --git a/docs/en/modules/identity/oauth-login.md b/docs/en/modules/identity/oauth-login.md
index f628ec8c7b..b36e35cfc1 100644
--- a/docs/en/modules/identity/oauth-login.md
+++ b/docs/en/modules/identity/oauth-login.md
@@ -9,7 +9,7 @@
## Introduction
-> You must have an ABP Team or a higher license to use this module & its features.
+> You must have an [ABP Team or a higher license](https://abp.io/pricing) to use this module & its features.
The Identity PRO module has built-in `OAuthExternalLoginProvider` service. It implements OAuth Resource Owner Password authentication and gets user info for [external login](https://github.com/abpframework/abp/issues/4977).
diff --git a/docs/en/modules/identity/periodic-password-change.md b/docs/en/modules/identity/periodic-password-change.md
index 4367ee88bb..2a5acf9634 100644
--- a/docs/en/modules/identity/periodic-password-change.md
+++ b/docs/en/modules/identity/periodic-password-change.md
@@ -9,7 +9,7 @@
## Introduction
-> You must have an ABP Team or a higher license to use this module & its features.
+> You must have an [ABP Team or a higher license](https://abp.io/pricing) to use this module & its features.
The Identity PRO module has a built-in password aging function.
diff --git a/docs/en/modules/identity/two-factor-authentication.md b/docs/en/modules/identity/two-factor-authentication.md
index 2acab6ec53..1ac4b5dd75 100644
--- a/docs/en/modules/identity/two-factor-authentication.md
+++ b/docs/en/modules/identity/two-factor-authentication.md
@@ -7,7 +7,7 @@
# Two Factor Authentication
-> You must have an ABP Team or a higher license to use this module & its features.
+> You must have an [ABP Team or a higher license](https://abp.io/pricing) to use this module & its features.
Two-factor authentication (**2FA**) is a specific type of multi-factor authentication (MFA) that requires the authenticating party to produce two separate identifying factors to verify your identity. The first factor is something you know "**username & password**" and the second factor is something you have "**mobile device or email**" to verify authentication requests. 2FA protects against phishing, social engineering and password brute-force attacks and secures your logins from attackers exploiting weak or stolen credentials.
diff --git a/docs/en/modules/language-management.md b/docs/en/modules/language-management.md
index 8ac9e6088e..a4c2968c2b 100644
--- a/docs/en/modules/language-management.md
+++ b/docs/en/modules/language-management.md
@@ -7,7 +7,7 @@
# Language Management Module (Pro)
-> You must have an ABP Team or a higher license to use this module.
+> You must have an [ABP Team or a higher license](https://abp.io/pricing) to use this module.
This module implements the Language management system of an application;
diff --git a/docs/en/modules/openiddict-pro.md b/docs/en/modules/openiddict-pro.md
index 5b681f6461..f531f65531 100644
--- a/docs/en/modules/openiddict-pro.md
+++ b/docs/en/modules/openiddict-pro.md
@@ -7,7 +7,7 @@
# OpenIddict Module (Pro)
-> You must have an ABP Team or a higher license to use this module.
+> You must have an [ABP Team or a higher license](https://abp.io/pricing) to use this module.
This module provides integration and management functionality for the OpenIddict library;
diff --git a/docs/en/modules/payment-custom-gateway.md b/docs/en/modules/payment-custom-gateway.md
index a17a225e09..df142f7a8c 100644
--- a/docs/en/modules/payment-custom-gateway.md
+++ b/docs/en/modules/payment-custom-gateway.md
@@ -7,7 +7,7 @@
# Creating a Custom Payment Gateway
-> You must have an ABP Team or a higher license to use this module.
+> You must have an [ABP Team or a higher license](https://abp.io/pricing) to use this module.
This document explains creating custom a payment gateway that's different than the existing ones in the [Payment Module](payment#packages).
diff --git a/docs/en/modules/payment.md b/docs/en/modules/payment.md
index b0d976b758..29654a2d42 100644
--- a/docs/en/modules/payment.md
+++ b/docs/en/modules/payment.md
@@ -7,7 +7,7 @@
# Payment Module (Pro)
-> You must have an ABP Team or a higher license to use this module.
+> You must have an [ABP Team or a higher license](https://abp.io/pricing) to use this module.
Payment module implements payment gateway integration of an application. It provides one time payment and recurring payment options.
diff --git a/docs/en/modules/saas.md b/docs/en/modules/saas.md
index d6faa4dbcb..cf88cf716a 100644
--- a/docs/en/modules/saas.md
+++ b/docs/en/modules/saas.md
@@ -7,7 +7,7 @@
# SaaS Module (Pro)
-> You must have an ABP Team or a higher license to use this module.
+> You must have an [ABP Team or a higher license](https://abp.io/pricing) to use this module.
This module is used to manage your tenants and editions in multi-tenant applications;
diff --git a/docs/en/modules/text-template-management.md b/docs/en/modules/text-template-management.md
index c0e19a0523..fa62ee7470 100644
--- a/docs/en/modules/text-template-management.md
+++ b/docs/en/modules/text-template-management.md
@@ -7,7 +7,7 @@
# Text Template Management Module (Pro)
-> You must have an ABP Team or a higher license to use this module.
+> You must have an [ABP Team or a higher license](https://abp.io/pricing) to use this module.
This module is used to store and edit template contents for [the text templating system](../framework/infrastructure/text-templating/index.md) of the ABP. So, you may need to understand it to better understand the purpose of this module.
diff --git a/docs/en/modules/twilio-sms.md b/docs/en/modules/twilio-sms.md
index 6ea6c7e93f..63ed91a148 100644
--- a/docs/en/modules/twilio-sms.md
+++ b/docs/en/modules/twilio-sms.md
@@ -7,7 +7,7 @@
# Twilio SMS Module (Pro)
-> You must have an ABP Team or a higher license to use this module.
+> You must have an [ABP Team or a higher license](https://abp.io/pricing) to use this module.
[Twilio](https://www.twilio.com) is a cloud communication provider that makes it easy to send and receive SMS. ABP Twilio SMS module implements the SMS sending feature of `ISmsSender` interface with Twilio.
diff --git a/docs/en/release-info/migration-guides/abp-10-0.md b/docs/en/release-info/migration-guides/abp-10-0.md
index c4b46a1edd..334adb2f4f 100644
--- a/docs/en/release-info/migration-guides/abp-10-0.md
+++ b/docs/en/release-info/migration-guides/abp-10-0.md
@@ -1,18 +1,43 @@
+```json
+//[doc-seo]
+{
+ "Description": "Upgrade your ABP solutions from v9.x to v10.0 with this comprehensive migration guide, ensuring compatibility and new features with .NET 10.0."
+}
+```
+
# ABP Version 10.0 Migration Guide
-This document is a guide for upgrading ABP v9.x solutions to ABP v10.0. There are some changes in this version that may affect your applications, please read it carefully and apply the necessary changes to your application.
+This document is a guide for upgrading ABP v9.x solutions to ABP v10.0. There are some changes in this version that may affect your applications. Please read them carefully and apply the necessary changes to your application.
## Open-Source (Framework)
-### Upgraded to .NET 10.0
+### Upgrade to .NET 10.0
+
+We've upgraded ABP to .NET 10.0, so you need to move your solutions to .NET 10.0 if you want to use ABP 10.0. You can check Microsoft’s [Migrate from ASP.NET Core 9.0 to 10.0](https://learn.microsoft.com/en-us/aspnet/core/migration/90-to-100) documentation to see how to update an existing ASP.NET Core 9.0 project to ASP.NET Core 10.0.
+
+### MySQL Support for .NET 10.0
+
+**If you are using MySQL as your database provider, please be aware of the following compatibility issues before upgrading to ABP 10.0!**
+
+The MySQL Entity Framework Core providers currently have limited support for .NET 10.0:
+
+* **Pomelo.EntityFrameworkCore.MySql**: Does not yet support .NET 10.0. The team is actively working on adding support.
+* **MySql.EntityFrameworkCore**: Currently in Release Candidate (RC) status with known bugs that may affect production applications.
+
+**Recommendation**: If you are using MySQL, we recommend waiting to upgrade to ABP 10.0 until the MySQL providers release stable versions with full .NET 10.0 support.
-We've upgraded ABP to .NET 10.0, so you need to move your solutions to .NET 10.0 if you want to use ABP 10.0. You can check Microsoft’s [Migrate from ASP.NET Core 9.0 to 10.0](https://learn.microsoft.com/en-us/aspnet/core/migration/90-to-100) documentation, to see how to update an existing ASP.NET Core 9.0 project to ASP.NET Core 10.0.
+**Track Progress**:
-### Add new EF Core Migrations
+* [Pomelo Provider - EF Core 10 Support](https://github.com/PomeloFoundation/Pomelo.EntityFrameworkCore.MySql/issues/2007)
+* [MySql.EntityFrameworkCore NuGet Package](https://www.nuget.org/packages/MySql.EntityFrameworkCore/#versions-body-tab)
+
+We will update to support the latest stable MySQL providers as soon as they become available.
+
+### Add New EF Core Migrations
Some entities in certain modules have been modified. If you are using Entity Framework Core, please create a new EF Core migration in your project after upgrading to ABP 10.0.
-> If the migration file is empty, you can remove it by `dotnet ef migrations remove` command.
+> If the migration file is empty, you can remove it by using the `dotnet ef migrations remove` command.
### Razor Runtime Compilation Obsolete
@@ -20,7 +45,13 @@ We removed the Razor Runtime Compilation support since it is obsolete and replac
If you want to keep using it, you can add [Microsoft.AspNetCore.Mvc.Razor.RuntimeCompilation](https://www.nuget.org/packages/Microsoft.AspNetCore.Mvc.Razor.RuntimeCompilation) package to your project and configure it manually.
+> If the referenced project also contains Razor Pages that require this feature, add the package to that project as well.
+
```csharp
+using Microsoft.AspNetCore.Mvc.Razor.RuntimeCompilation;
+using Volo.Abp.DependencyInjection;
+using Volo.Abp.AspNetCore.VirtualFileSystem;
+
public override void ConfigureServices(ServiceConfigurationContext context)
{
if (context.Services.GetHostingEnvironment().IsDevelopment())
@@ -42,31 +73,25 @@ For more information, you can check the [Razor Runtime Compilation Obsolete](htt
### IActionContextAccessor Obsolete
-We removed the `IActionContextAccessor` from dependency injection.
-
-> We are not using `IActionContextAccessor` in ABP core framework and modules.
+We removed the `IActionContextAccessor` from dependency injection and are not using the `IActionContextAccessor` in ABP's core framework and modules.
See [IActionContextAccessor Obsolete](https://learn.microsoft.com/en-us/dotnet/core/compatibility/aspnet-core/10/iactioncontextaccessor-obsolete) for more information.
### Add `BLOB Storing Memory Provider` module.
-In this version, we added the `BLOB Storing Memory Provider` module for unit testing purposes.
+In this version, we have added the `BLOB Storing Memory Provider` module for unit testing purposes.
See the [BLOB Storing Memory Provider](https://github.com/abpframework/abp/blob/dev/docs/en/framework/infrastructure/blob-storing/memory.md) document for more information.
### Always use `MapStaticAssets`
-Provious, the `MapStaticAssets` has performance problems if there are too many static files. and we will use `StaticFileMiddleware` to serve the static files in development mode. NET 10.0 has fixed this problem. We will always use `MapStaticAssets` to serve the static files.
+Previously, the `MapStaticAssets` had performance problems if there were too many static files. NET 10.0 has fixed this problem. We will always use `MapStaticAssets` to serve the static files.
See [Static file serving performance issues](https://github.com/dotnet/aspnetcore/issues/59673) for more information.
### C# 14 overload resolution with span parameters
-NET Core will redirect `array.Contains` extension method to `MemoryExtensions.Contains`, This will cause `MongoDB.Driver` to be unable to translate `IQueryable`, If you are using `array.Contains` in your code, you should use following code to avoid this problem.
-
-> Only array has this problem, other types are not affected. eg List, HashSet, etc.
-
-> MongoDB.Driver will be fixed in the future.
+NET Core will redirect the `array.Contains` extension method to `MemoryExtensions.Contains`. This will cause `MongoDB.Driver` to be unable to translate `IQueryable`. If you are using `array.Contains` in your code, you should use the following code to avoid this problem:
```csharp
M((array, num) => array.Contains(num)); // fails, binds to MemoryExtensions.Contains
@@ -75,13 +100,15 @@ M((array, num) => array.AsEnumerable().Contains(num)); // ok, binds to Enumerabl
M((array, num) => Enumerable.Contains(array, num)); // ok, binds to Enumerable.Contains
```
+> Please note that only the `array` type has this problem. Other types are not affected (e.g. `List`, `HashSet`, etc). **MongoDB.Driver** provider will be fixed in future versions, and we will immediately apply the changes if needed.
+
See the [C# 14 overload resolution with span parameters](https://learn.microsoft.com/en-us/dotnet/core/compatibility/core-libraries/10.0/csharp-overload-resolution#recommended-action) for more information.
-### OpenIddict 7.X
+### OpenIddict Upgrade to 7.X
-We upgraded OpenIddict to 7.X. See the [OpenIddict 6.x to 7.x Migration Guide](https://documentation.openiddict.com/guides/migration/60-to-70.html) for more information.
+We have upgraded **OpenIddict** to **v7.x**. For detailed information about the changes introduced in this release, refer to the [OpenIddict 6.x to 7.x Migration Guide](https://documentation.openiddict.com/guides/migration/60-to-70.html).
-OpenIddict 7.X changed the `OpenIddictToken` entity, you must create a new database migration if you use Entity Framework Core.
+As a developer, you typically only need to **create a new Entity Framework Core migration** and **apply it to your database**, since **OpenIddict v7.x** introduces a modification in the `OpenIddictToken` entity.
### Migrating from AutoMapper to Mapperly
@@ -107,6 +134,3 @@ Starting from **ABP 10.0**, the [`HideErrors`](../../framework/fundamentals/cach
By default, ABP hides and logs cache server errors to keep the application running even when the cache is unavailable.
However, in the **development environment**, errors are no longer hidden so that developers can immediately detect and fix **any cache server issues** (such as connection, configuration, or runtime errors).
-
-## PRO
-
diff --git a/docs/en/release-info/migration-guides/abp-5-0-angular.md b/docs/en/release-info/migration-guides/abp-5-0-angular.md
index f6abcf10f6..66627b1e8a 100644
--- a/docs/en/release-info/migration-guides/abp-5-0-angular.md
+++ b/docs/en/release-info/migration-guides/abp-5-0-angular.md
@@ -104,7 +104,7 @@ If you don't want to use the NGXS, you should remove all NGXS related imports, i
## @angular/localize package
-[`@angular/localize`](https://angular.io/api/localize) dependency has been removed from `@abp/ng.core` package. The package must be installed in your app. Run the following command to install:
+[`@angular/localize`](https://angular.dev/guide/i18n/add-package) dependency has been removed from `@abp/ng.core` package. The package must be installed in your app. Run the following command to install:
```bash
npm install @angular/localize@12
diff --git a/docs/en/release-info/release-notes.md b/docs/en/release-info/release-notes.md
index cb6d5f421d..bf335fa7a2 100644
--- a/docs/en/release-info/release-notes.md
+++ b/docs/en/release-info/release-notes.md
@@ -14,9 +14,21 @@ Also see the following notes about ABP releases:
* [ABP Studio release notes](../studio/release-notes.md)
* [Change logs for ABP pro packages](https://abp.io/pro-releases)
+## 10.0 (2025-11-18)
+
+See the detailed **[blog post / announcement](https://abp.io/community/announcements/abp.io-platform-10.0-final-has-been-released-spknn925)** for the v10.0 release.
+
+* Upgraded to .NET 10.0
+* Upgraded to `Blazorise` **v1.8.6**
+* New PRO Module: [Elsa Workflows](../modules/elsa-pro.md)
+* New Object Mapper: **Mapperly**
+* Localization: Nested Object Support in JSON Files
+* EF Core Shared Entity Types on Repositories
+* Angular SSR Support
+
## 9.3 (2025-06-17)
-This is currently a RC (release-candidate) and you can see the detailed **[blog post / announcement](https://abp.io/community/articles/announcing-abp-9-3-release-candidate-4dqgiryf)** for the v9.3 release.
+See the detailed **[blog post / announcement](https://abp.io/community/announcements/announcing-abp-9-3-stable-release-fw4n9sng)** for the v9.3 release.
* Cron Expression Support for Background Workers
* Docs Module: PDF Export
diff --git a/docs/en/release-info/road-map.md b/docs/en/release-info/road-map.md
index f7b432a39d..0df94ec157 100644
--- a/docs/en/release-info/road-map.md
+++ b/docs/en/release-info/road-map.md
@@ -11,36 +11,39 @@ This document provides a road map, release schedule, and planned features for th
## Next Versions
-### v10.0
+### v10.1
-The next version will be 10.0 and planned to release the stable 10.0 version in December 2025. We will be mostly working on the following topics:
+The next version will be 10.1 and planned to release the stable 10.1 version in January 2026. We will be mostly working on the following topics:
* Framework
- * Upgrading to .NET 10
- * Upgrading 3rd-party dependencies
- * Enhancements in the core points
+ * OpenTelemetry Protocol Support for 3rd-party Integrations
+ * Resource Based Authorization Integration
+ * Upgrading 3rd-party Dependencies
+ * Enhancements in the Core Points
* ABP Suite
- * Define navigation properties without target string property dependency
- * Improvements one-to-many scenarios
- * File Upload Modal enhancements
-
+ * Define Navigation Properties Without Target String Property Dependency
+ * Improvements on Master-Detail Page Desing (making it more compact)
+ * Improvements One-To-Many Scenarios
+ * File Upload Modal Enhancements
* ABP Studio
- * Allow to directly create new solutions with ABP's RC (Release Candidate) versions
- * Automate more details on new service creation for a microservice solution
- * Support multiple concurrent Kubernetes deployment/integration scenarios
- * Improve the module installation experience / installation guides
- * Improve client proxy generation experience
- * Modular Monolith Application Startup Template
-
-* Application modules
- * Account module: Support mixed social/local login scenarios & adding security related features
- * UI/UX improvements on existing application modules
-
-* Updating existing tutorials & documents (with other UI & DB options)
- * Microservice development
- * Modular monolith development
+ * Allow to Directly Create New Solutions with ABP's RC (Release Candidate) Versions
+ * Automate More Details on New Service Creation for a Microservice Solution
+ * Allow to Download ABP Samples from ABP Studio
+ * Task Panel Enhancements (and Documentation)
+ * Support Multiple Concurrent Kubernetes Deployment/Integration Scenarios
+ * Improve the Module Installation Experience / Installation Guides
+
+* Application Modules
+ * Payment Module: Public Page Implementation (for Blazor & Angular UIs)
+ * AI Management Module: UI Implementation for Blazor & Angular UIs
+ * CMS Kit: Enhancements for Some Features (Rating, Dynamic Widgets, FAQ and more...)
+ * UI/UX Improvements on Existing Application Modules
+
+* Updating Existing Tutorials & Documents (with Other UI & DB Options)
+ * Microservice Development
+ * Modular Monolith Development
## Backlog Items
@@ -50,7 +53,6 @@ The *Next Versions* section above shows the main focus of the planned versions.
The ABP framework is [open source](https://github.com/abpframework/abp) and free for everyone. You can see its [public backlog](https://github.com/abpframework/abp/milestone/2). Here, are some of the important features you can expect from next versions:
-* [#236](https://github.com/abpframework/abp/issues/236) / Resource based authorization system
* [#2882](https://github.com/abpframework/abp/issues/2882) / Providing a gRPC integration infrastructure (while it is [already possible](https://github.com/abpframework/abp-samples/tree/master/GrpcDemo) to create or consume gRPC endpoints for your application, we plan to create endpoints for the [standard application modules](../modules/index.md))
* [#57](https://github.com/abpframework/abp/issues/57) / Built-in CQRS infrastructure
* [#58](https://github.com/abpframework/abp/issues/58) / Content localization system (multilingual entities)
@@ -85,12 +87,9 @@ Here, are some of the important planned features for next ABP Studio versions:
* Analyze user solutions to explore entities, domain services, application services, pages and other fundamental objects.
* Swagger authentication support for the built-in browser
* Show related requests/events (traces) together in the solution runner panel
-* Integrate common tool dashboards into ABP Studio (such a Garana, Redis, RabbitMQ, Kibana, etc)
* Built-in command terminal
* Automate all steps of new service creation for microservice solutions
-* Container application type support for Solution Runner (to individually control docker dependencies)
* More options while creating new solutions
-* Downloading samples in ABP studio
* Built-in ABP documentation experience
* Auto-execute terminal commands in markdown files
* Compare changes on the startup templates when a new ABP version is published
diff --git a/docs/en/samples/easy-crm.md b/docs/en/samples/easy-crm.md
index eb959a38c8..7aee565171 100644
--- a/docs/en/samples/easy-crm.md
+++ b/docs/en/samples/easy-crm.md
@@ -30,7 +30,7 @@ When you download and open the zip file, you will see two folders:
### Server Side / MVC (Razor Pages) Application
-* Open the solution (inside the aspnet-core folder) in **Visual Studio 2019** or later (or with another IDE that supports ASP.NET Core).
+* Open the solution (inside the aspnet-core folder) in **Visual Studio 2026** or later (or with another IDE that supports ASP.NET Core).
* This project use `Sqlite`, the default database folder is located at appsettings (`"SqliteDbFolder": "sqliteDbs"`, this folder is located in the MVC project).
* Open the `appsettings.json` file in the `Volo.EasyCrm.Web` application and set `"UseDynamicDatabase": "false"`.
> The MVC project is creating new database for each unique visitor. And the visitor id is stored at cookies. When you set `UseDynamicDatabase` as a `true`, you cannot run Blazor & Angular projects because they have no cookie implementation. Be aware it is set as `false` for running Blazor & Angular applications.
diff --git a/docs/en/samples/microservice-demo.md b/docs/en/samples/microservice-demo.md
index 31516b2a55..c31959f6b0 100644
--- a/docs/en/samples/microservice-demo.md
+++ b/docs/en/samples/microservice-demo.md
@@ -60,7 +60,7 @@ To be able to run the solution from source code, following tools should be insta
### Open & Build the Visual Studio Solution
-* Open the `samples\MicroserviceDemo\MicroserviceDemo.sln` in Visual Studio 2017 (15.9.0+).
+* Open the `samples\MicroserviceDemo\MicroserviceDemo.sln` in Visual Studio 2026 (18.0.0+).
* Run `dotnet restore` from the command line inside the `samples\MicroserviceDemo` folder.
* Build the solution in Visual Studio.
diff --git a/docs/en/solution-templates/layered-web-application/mobile-applications.md b/docs/en/solution-templates/layered-web-application/mobile-applications.md
index 5d3c1385f4..553064284f 100644
--- a/docs/en/solution-templates/layered-web-application/mobile-applications.md
+++ b/docs/en/solution-templates/layered-web-application/mobile-applications.md
@@ -21,7 +21,7 @@
}
```
-> You must have an ABP Team or a higher license to be able to create a mobile application project with ABP Studio.
+> You must have an [ABP Team or a higher license](https://abp.io/pricing) to be able to create a mobile application project with ABP Studio.
Mobile applications are an essential part of modern software solutions. They provide a user-friendly interface to the end-users and allow them to access the system from anywhere. ABP Studio allows you to create mobile applications for your layered solution. You can create a new mobile application project, configure it, and run it on your device.
diff --git a/docs/en/solution-templates/layered-web-application/web-applications.md b/docs/en/solution-templates/layered-web-application/web-applications.md
index 58cc3af078..8400a6dfbe 100644
--- a/docs/en/solution-templates/layered-web-application/web-applications.md
+++ b/docs/en/solution-templates/layered-web-application/web-applications.md
@@ -120,7 +120,7 @@ The required style files are added to the `styles` array in `angular.json`. `App
You should create your tests in the same folder as the file you want to test.
-See the [testing document](https://angular.io/guide/testing).
+See the [testing document](https://angular.dev/guide/testing).
### Depended Packages
diff --git a/docs/en/studio/installation.md b/docs/en/studio/installation.md
index 1b1ba2cf04..6f12953f99 100644
--- a/docs/en/studio/installation.md
+++ b/docs/en/studio/installation.md
@@ -11,7 +11,7 @@ This document explains how to install the ABP Studio tool.
## Pre-requirements
-ABP Studio automatically instals most of the required dependencies. When you first launch the application, it will check for and install the following components if missed:
+ABP Studio automatically installs most of the required dependencies. When you first launch the application, it will check for and install the following components if missed:
* .NET SDK
* Node.js
@@ -19,7 +19,7 @@ ABP Studio automatically instals most of the required dependencies. When you fir
* mkcert (for HTTPS development)
* WireGuard (for Kubernetes operations)
-However, the followings should be manually installed:
+However, the following should be manually installed:
### Docker (Required for Kubernetes Operations)
@@ -55,7 +55,7 @@ ABP Studio allows you to customize the user interface theme according to your pr
## Upgrading
ABP Studio periodically checks for updates in the background, and when a new version of ABP Studio is available, you will be notified through a modal.
-The modal will prompt you to update to the latest version as below:
+The modal will prompt you to update to the latest version as follows:

diff --git a/docs/en/studio/release-notes.md b/docs/en/studio/release-notes.md
index b0627a887e..c3f57deaaf 100644
--- a/docs/en/studio/release-notes.md
+++ b/docs/en/studio/release-notes.md
@@ -9,6 +9,41 @@
This document contains **brief release notes** for each ABP Studio release. Release notes only include **major features** and **visible enhancements**. Therefore, they don't include all the development done in the related version.
+## 1.4.2 (2025-10-30)
+
+* Upgraded template dependencies for ABP Framework and LeptonX. (targeting ABP `9.3.6`)
+* AI Assistant is now enabled for all customers.
+* Fixed CLI default language problem during solution creation.
+* Improved task auto-start logic and notification handling.
+* Fixed Angular localization function inputs.
+* Set default mobile frameworks to **None** in the UI.
+* Disallowed dots (.) in module names of microservice sub-templates.
+* Solution Runner: show vertical scrollbar when needed and disable the Properties window while the app is running.
+
+## 1.4.1 (2025-10-16)
+
+* Fixed AI Assistant chat problems.
+* Added custom steps if built with CLI.
+* Fixed Release configuration builds.
+
+## 1.4.0 (2025-10-15)
+
+* The **Task Panel** has been introduced, providing a centralized place to manage and monitor background operations.
+* Added **CLI application properties** window, making it easier to configure and manage command-line tool settings directly within the Studio UI.
+* Added suggestion modal for building after creating service/web/gateway module.
+* Fixed mismatching hosts file record namespace problem.
+* Allow selecting `Default Profile` in Solution Runner.
+* Refactored Angular scripts.
+* Fixed: tools not browsable in Solution Runner with Aspire after Kubernetes deployment.
+
+## 1.3.3 (2025-10-06)
+
+* Upgraded template dependencies for ABP Framework and LeptonX. (targeting ABP `9.3.5`)
+* Fixed welcome page tutorial links.
+* Improved error handling during Helm chart installation and custom command execution.
+* Fixed microservice problems.
+* Fixed connection string problems.
+
## 1.3.2 (2025-09-25)
* Enhanced AI Assistant with bug fixes and improvements.
diff --git a/docs/en/studio/version-mapping.md b/docs/en/studio/version-mapping.md
index 6bd879f2ab..ba51cfb17d 100644
--- a/docs/en/studio/version-mapping.md
+++ b/docs/en/studio/version-mapping.md
@@ -11,6 +11,8 @@ This document provides a general overview of the relationship between various ve
| **ABP Studio Version** | **ABP Version of Startup Template** |
|------------------------|---------------------------|
+| 1.4.2 | 9.3.6 |
+| 1.3.3 to 1.4.1 | 9.3.5 |
| 1.3.0 - 1.3.2 | 9.3.4 |
| 1.2.2 | 9.3.2 |
| 1.2.1 | 9.3.1 |
diff --git a/docs/en/suite/editing-templates.md b/docs/en/suite/editing-templates.md
index 9c859ba0de..354adc8ead 100644
--- a/docs/en/suite/editing-templates.md
+++ b/docs/en/suite/editing-templates.md
@@ -27,7 +27,7 @@ There's a search box on the templates page. To find the related template, pick a
There's a naming convention for the template files.
* If the template name has `Server` prefix, it's used for backend code like repositories, application services, localizations, controllers, permissions, mappings, unit tests.
-* If the template name has `Frontend.Angular` prefix, it's used for Angular code generation. The Angular code is being generated via [Angular Schematics](https://angular.io/guide/schematics).
+* If the template name has `Frontend.Angular` prefix, it's used for Angular code generation. The Angular code is being generated via [Angular Schematics](https://angular.dev/tools/cli/schematics).
* If the template name has `Frontend.Mvc` prefix, it's used for razor pages, menus, JavaScript, CSS files.
* If the template name has `Frontend.Blazor` prefix, it's used for razor components.
diff --git a/docs/en/suite/generating-crud-page.md b/docs/en/suite/generating-crud-page.md
index cc9df3ee32..afc2536709 100644
--- a/docs/en/suite/generating-crud-page.md
+++ b/docs/en/suite/generating-crud-page.md
@@ -294,7 +294,7 @@ There are some adjustments you may need to make before generating CRUD pages for
- Check if your environment variables have `rootNamespace` defined as explained [here](../framework/ui/angular/service-proxies.md#angular-project-configuration).
-- Check if your [workspace configuration](https://angular.io/guide/workspace-config) satisfies one of the following. Examples assume your solution namespace is `BookStore`, `Acme.BookStore`, or `Acme.Retail.BookStore`.
+- Check if your [workspace configuration](https://angular.dev/reference/configs/workspace-config) satisfies one of the following. Examples assume your solution namespace is `BookStore`, `Acme.BookStore`, or `Acme.Retail.BookStore`.
- Project key is in pascal case. E.g. `BookStore`.
- Project key is in camel case. E.g. `bookStore`.
- Project key is in kebab case. E.g. `book-store`.
diff --git a/docs/en/suite/index.md b/docs/en/suite/index.md
index 20005ecb21..b1c8d43fa7 100644
--- a/docs/en/suite/index.md
+++ b/docs/en/suite/index.md
@@ -17,7 +17,7 @@
}
````
-> You must have an ABP Team or a higher license to use the ABP Suite.
+> You must have an [ABP Team or a higher license](https://abp.io/pricing) to use the ABP Suite.
ABP Suite is a complementary tool to the ABP Platform. ABP Suite allows you to build web pages in a matter of minutes.
diff --git a/docs/en/suite/solution-structure.md b/docs/en/suite/solution-structure.md
index d36ea35e7f..4b15be2f07 100644
--- a/docs/en/suite/solution-structure.md
+++ b/docs/en/suite/solution-structure.md
@@ -303,7 +303,7 @@ Lepton theme uses two logos for each style. You can change these logos with your
You should create your tests in the same folder as the file file you want to test.
-See the [testing document](https://angular.io/guide/testing).
+See the [testing document](https://angular.dev/guide/testing).
### Depended Packages
diff --git a/docs/en/testing/integration-tests.md b/docs/en/testing/integration-tests.md
index dce7813e45..c87d270747 100644
--- a/docs/en/testing/integration-tests.md
+++ b/docs/en/testing/integration-tests.md
@@ -350,7 +350,7 @@ There are multiple overloads of the `WithUnitOfWorkAsync` method that you can us
## Working with DbContext
-In some cases, you may want to directory work with the [Entity Framework's `DbContext` object](https://learn.microsoft.com/en-us/dotnet/api/system.data.entity.dbcontext) to perform database operations in your test methods. In this case, you can use `IDbContextProvider`service to obtain a `DbContext` instance inside a unit of work.
+In some cases, you may want to directly work with the [Entity Framework's `DbContext` object](https://learn.microsoft.com/en-us/dotnet/api/system.data.entity.dbcontext) to perform database operations in your test methods. In this case, you can use `IDbContextProvider`service to obtain a `DbContext` instance inside a unit of work.
The following example shows how you can create a `DbContext` object in a test method:
diff --git a/docs/en/tutorials/book-store-with-abp-suite/index.md b/docs/en/tutorials/book-store-with-abp-suite/index.md
index 9a2f9372b7..204380bdf0 100644
--- a/docs/en/tutorials/book-store-with-abp-suite/index.md
+++ b/docs/en/tutorials/book-store-with-abp-suite/index.md
@@ -46,4 +46,4 @@ This tutorial is organized as the following parts:
### Download the Source Code
-After logging in to the ABP website, you can download the source code from [here](https://abp.io/api/download/samples/suite-bookstore-mvc-ef).
\ No newline at end of file
+After logging in to the ABP website, you can download the source code from [here](https://abp.io/api/download/samples/bookstore-mvc-ef).
diff --git a/docs/en/tutorials/book-store-with-abp-suite/part-02.md b/docs/en/tutorials/book-store-with-abp-suite/part-02.md
index b18e7e515b..11725201cb 100644
--- a/docs/en/tutorials/book-store-with-abp-suite/part-02.md
+++ b/docs/en/tutorials/book-store-with-abp-suite/part-02.md
@@ -135,10 +135,12 @@ It will take some time to complete the process. After the process is completed,
{{ end }}
-After the application is started, you can right-click and *Browse* on the application to open it in the ABP Studio's pre-integrated browser. After logging in using the default credentials (`admin` / `1q2w3E*`), you can see the Books page in the following figure with a single record:
+After the application is started, you can right-click and *Browse* on the application to open it in the ABP Studio's pre-integrated browser. After logging in using the default credentials (`admin` / `1q2w3E*`), you can see the Books page like in the following figure:

+> By default, ABP Suite doesn't generate data seed contributors for entities, as you'll need to create them manually. This is intentional since having dummy data in development or production environments may not be suitable for your specific needs. However, if you selected the **Create unit & integration tests** option while creating the entity, you can see the sample data-seed contributors under the *Acme.BookStore.Domain.Tests* project to simplify the testing process by having initial data for the entities, which we will see in [the part 4 of this tutorial](part-04.md).
+
On this page, you can create a new book, update an existing book, delete a book, export all records (or the filtered records) to excel, filter the records by using the advanced filter section, bulk delete multiple records and so on.
## Summary
diff --git a/docs/en/tutorials/book-store/part-02.md b/docs/en/tutorials/book-store/part-02.md
index 9f52a6ddaa..1fe21c2848 100644
--- a/docs/en/tutorials/book-store/part-02.md
+++ b/docs/en/tutorials/book-store/part-02.md
@@ -315,7 +315,7 @@ This is a fully working, server side paged, sorted and localized table of books.
## Install NPM packages
-> Notice: This tutorial is based on the ABP v3.1.0+ If your project version is older, then please upgrade your solution. Check the [migration guide](../../framework/ui/angular/migration-guide-v3.md) if you are upgrading an existing project with v2.x.
+> Notice: This tutorial is based on the ABP v9.3.0+ If your project version is older, then please upgrade your solution. Check the [migration guide](../../framework/ui/angular/migration-guide-v3.md) if you are upgrading an existing project with v2.x.
If you haven't done it before, open a new command line interface (terminal window) and go to your `angular` folder and then run the `yarn` command to install the NPM packages:
@@ -330,69 +330,42 @@ It's time to create something visible and usable! There are some tools that we w
- [Ng Bootstrap](https://ng-bootstrap.github.io/#/home) will be used as the UI component library.
- [Ngx-Datatable](https://swimlane.gitbook.io/ngx-datatable/) will be used as the datatable library.
-Run the following command line to create a new module, named `BookModule` in the root folder of the angular application:
+Run the following command line to create a new component, named `BookComponent` in the root folder of the angular application:
```bash
-yarn ng generate module book --module app --routing --route books
+yarn ng generate component book
```
This command should produce the following output:
````bash
-> yarn ng generate module book --module app --routing --route books
-
-yarn run v1.19.1
-$ ng generate module book --module app --routing --route books
-CREATE src/app/book/book-routing.module.ts (336 bytes)
-CREATE src/app/book/book.module.ts (335 bytes)
-CREATE src/app/book/book.component.html (19 bytes)
-CREATE src/app/book/book.component.spec.ts (614 bytes)
-CREATE src/app/book/book.component.ts (268 bytes)
+> yarn ng generate component book
+
+yarn run v1.22.22
+$ ng generate component book
+CREATE src/app/book/book.component.spec.ts (537 bytes)
+CREATE src/app/book/book.component.ts (189 bytes)
CREATE src/app/book/book.component.scss (0 bytes)
-UPDATE src/app/app-routing.module.ts (1289 bytes)
+CREATE src/app/book/book.component.html (20 bytes)
Done in 3.88s.
````
-### BookModule
-
-Open the `/src/app/book/book.module.ts` and replace the content as shown below:
-
-````js
-import { NgModule } from '@angular/core';
-import { SharedModule } from '../shared/shared.module';
-import { BookRoutingModule } from './book-routing.module';
-import { BookComponent } from './book.component';
-
-@NgModule({
- declarations: [BookComponent],
- imports: [
- BookRoutingModule,
- SharedModule
- ]
-})
-export class BookModule { }
-
-````
-
-* Added the `SharedModule`. `SharedModule` exports some common modules needed to create user interfaces.
-* `SharedModule` already exports the `CommonModule`, so we've removed the `CommonModule`.
-
### Routing
-The generated code places the new route definition to the `src/app/app-routing.module.ts` file as shown below:
+The generated code places the new route definition to the `src/app/app.routes.ts` file as shown below:
````js
-const routes: Routes = [
+export const routes: Routes = [
// other route definitions...
- { path: 'books', loadChildren: () => import('./book/book.module').then(m => m.BookModule) },
+ { path : 'books', loadComponent: () => import('./book/book.component').then(c => c.BookComponent) },
];
````
Now, open the `src/app/route.provider.ts` file and replace the `configureRoutes` function declaration as shown below:
```js
-function configureRoutes(routes: RoutesService) {
- return () => {
+function configureRoutes() {
+ const routes = inject(RoutesService);
routes.add([
{
path: '/',
@@ -416,7 +389,6 @@ function configureRoutes(routes: RoutesService) {
},
]);
};
-}
```
`RoutesService` is a service provided by the ABP to configure the main menu and the routes.
@@ -497,7 +469,7 @@ Open the `/src/app/book/book.component.html` and replace the content as shown be
-
+
{%{{{ '::Enum:BookType.' + row.type | abpLocalization }}}%}
@@ -522,7 +494,7 @@ Now you can see the final result on your browser:

-{{else if UI == "Blazor" || UI == "BlazorServer" || UI == "BlazorWebApp"}}
+{{else if UI == "Blazor" || UI == "BlazorServer" || UI == "BlazorWebApp" || UI == "MAUIBlazor"}}
## Create a Books Page
diff --git a/docs/en/tutorials/book-store/part-03.md b/docs/en/tutorials/book-store/part-03.md
index 546b4a743d..73b2daea4e 100644
--- a/docs/en/tutorials/book-store/part-03.md
+++ b/docs/en/tutorials/book-store/part-03.md
@@ -670,7 +670,7 @@ You can open your browser and click the **New book** button to see the new modal
### Create a Reactive Form
-[Reactive forms](https://angular.io/guide/reactive-forms) provide a model-driven approach to handling form inputs whose values change over time.
+[Reactive forms](https://angular.dev/guide/forms/reactive-forms) provide a model-driven approach to handling form inputs whose values change over time.
Open `/src/app/book/book.component.ts` and replace the content as below:
@@ -742,8 +742,8 @@ export class BookComponent implements OnInit {
* Imported `FormGroup`, `FormBuilder` and `Validators` from `@angular/forms`.
* Added a `form: FormGroup` property.
* Added a `bookTypes` property as a list of `BookType` enum members. That will be used in form options.
-* Injected with the `FormBuilder` inject function.. [FormBuilder](https://angular.io/api/forms/FormBuilder) provides convenient methods for generating form controls. It reduces the amount of boilerplate needed to build complex forms.
-* Added a `buildForm` method to the end of the file and executed the `buildForm()` in the `createBook` method.
+* Injected the `FormBuilder` with the inject function. [FormBuilder](https://angular.dev/api/forms/FormBuilder) provides convenient methods for generating form controls. It reduces the amount of boilerplate that is needed to build complex forms.
+* Added a `buildForm` method at the end of the file and executed the `buildForm()` in the `createBook` method.
* Added a `save` method.
Open `/src/app/book/book.component.html` and replace `` with the following code part:
@@ -765,7 +765,11 @@ Open `/src/app/book/book.component.html` and replace ` Type *
@@ -804,46 +808,24 @@ Also replace `` with the following code p
We've used [NgBootstrap datepicker](https://ng-bootstrap.github.io/#/components/datepicker/overview) in this component. So, we need to arrange the dependencies related to this component.
-Open `/src/app/book/book.module.ts` and replace the content as below:
-
-```js
-import { NgModule } from '@angular/core';
-import { SharedModule } from '../shared/shared.module';
-import { BookRoutingModule } from './book-routing.module';
-import { BookComponent } from './book.component';
-import { NgbDatepickerModule } from '@ng-bootstrap/ng-bootstrap'; // add this line
-
-@NgModule({
- declarations: [BookComponent],
- imports: [
- BookRoutingModule,
- SharedModule,
- NgbDatepickerModule, // add this line
- ]
-})
-export class BookModule { }
-```
-
-* We imported `NgbDatepickerModule` to be able to use the date picker.
-
Open `/src/app/book/book.component.ts` and replace the content as below:
```js
import { ListService, PagedResultDto } from '@abp/ng.core';
import { Component, OnInit, inject } from '@angular/core';
import { BookService, BookDto, bookTypeOptions } from '@proxy/books';
-import { FormGroup, FormBuilder, Validators } from '@angular/forms';
-
-// added this line
-import { NgbDateNativeAdapter, NgbDateAdapter } from '@ng-bootstrap/ng-bootstrap';
+import { FormGroup, FormBuilder, Validators, ReactiveFormsModule } from '@angular/forms';
+import { NgbDateNativeAdapter, NgbDateAdapter, NgbDatepickerModule } from '@ng-bootstrap/ng-bootstrap';
+import { ThemeSharedModule } from '@abp/ng.theme.shared';
@Component({
selector: 'app-book',
templateUrl: './book.component.html',
styleUrls: ['./book.component.scss'],
+ imports: [ThemeSharedModule, ReactiveFormsModule, NgbDatepickerModule],
providers: [
ListService,
- { provide: NgbDateAdapter, useClass: NgbDateNativeAdapter } // add this line
+ { provide: NgbDateAdapter, useClass: NgbDateNativeAdapter }
],
})
export class BookComponent implements OnInit {
diff --git a/docs/en/tutorials/book-store/part-05.md b/docs/en/tutorials/book-store/part-05.md
index b7b05103c9..3db00ea423 100644
--- a/docs/en/tutorials/book-store/part-05.md
+++ b/docs/en/tutorials/book-store/part-05.md
@@ -311,23 +311,19 @@ We've only added the `.RequirePermissions(BookStorePermissions.Books.Default)` e
First step of the UI is to prevent unauthorized users to see the "Books" menu item and enter to the book management page.
-Open the `/src/app/book/book-routing.module.ts` and replace with the following content:
+Open the `/src/app/app.routes.ts` and replace with the following content:
````js
-import { NgModule } from '@angular/core';
-import { Routes, RouterModule } from '@angular/router';
import { authGuard, permissionGuard } from '@abp/ng.core';
import { BookComponent } from './book.component';
const routes: Routes = [
- { path: '', component: BookComponent, canActivate: [authGuard, permissionGuard] },
+{
+ path: 'books',
+ loadComponent: () => import('./book/book.component').then(c => BookComponent),
+ canActivate: [authGuard, permissionGuard],
+},
];
-
-@NgModule({
- imports: [RouterModule.forChild(routes)],
- exports: [RouterModule],
-})
-export class BookRoutingModule {}
````
* Imported `authGuard` and `permissionGuard` from the `@abp/ng.core`.
diff --git a/docs/en/tutorials/book-store/part-09.md b/docs/en/tutorials/book-store/part-09.md
index c30b018494..b70fd3e875 100644
--- a/docs/en/tutorials/book-store/part-09.md
+++ b/docs/en/tutorials/book-store/part-09.md
@@ -477,49 +477,43 @@ That's all! You can run the application and try to edit an author.
## The Author Management Page
-Run the following command line to create a new module, named `AuthorModule` in the root folder of the angular application:
+Run the following command line to create a new component, named `AuthorComponent` in the root folder of the angular application:
```bash
-yarn ng generate module author --module app --routing --route authors
+yarn ng generate component author
```
This command should produce the following output:
```bash
-> yarn ng generate module author --module app --routing --route authors
+> yarn ng generate component author
yarn run v1.19.1
-$ ng generate module author --module app --routing --route authors
-CREATE src/app/author/author-routing.module.ts (344 bytes)
-CREATE src/app/author/author.module.ts (349 bytes)
+$ yarn ng generate component author
CREATE src/app/author/author.component.html (21 bytes)
CREATE src/app/author/author.component.spec.ts (628 bytes)
CREATE src/app/author/author.component.ts (276 bytes)
CREATE src/app/author/author.component.scss (0 bytes)
-UPDATE src/app/app-routing.module.ts (1396 bytes)
Done in 2.22s.
```
-### AuthorModule
+### Author Component
-Open the `/src/app/author/author.module.ts` and replace the content as shown below:
+Open the `/src/app/author/author.component.ts` and replace the content as shown below:
```js
-import { NgModule } from '@angular/core';
-import { SharedModule } from '../shared/shared.module';
-import { AuthorRoutingModule } from './author-routing.module';
-import { AuthorComponent } from './author.component';
+import { Component } from '@angular/core';
import { NgbDatepickerModule } from '@ng-bootstrap/ng-bootstrap';
-@NgModule({
- declarations: [AuthorComponent],
- imports: [SharedModule, AuthorRoutingModule, NgbDatepickerModule],
+@Component({
+ selector: 'app-author',
+ templateUrl: './author.component.html',
+ styleUrls: ['./author.component.scss'],
+ imports: [NgbDatepickerModule],
})
-export class AuthorModule {}
+export class AuthorComponent {}
```
-- Added the `SharedModule`. `SharedModule` exports some common modules needed to create user interfaces.
-- `SharedModule` already exports the `CommonModule`, so we've removed the `CommonModule`.
- Added `NgbDatepickerModule` that will be used later on the author create and edit forms.
### Menu Definition
@@ -753,13 +747,13 @@ Open the `/src/app/author/author.component.html` and replace the content as belo
-
+
{%{{{ row.birthDate | date }}}%}
-
+
diff --git a/docs/en/tutorials/book-store/part-10.md b/docs/en/tutorials/book-store/part-10.md
index 5e0235ad14..e03ada5a96 100644
--- a/docs/en/tutorials/book-store/part-10.md
+++ b/docs/en/tutorials/book-store/part-10.md
@@ -970,7 +970,7 @@ Book list page change is trivial. Open the `/src/app/book/book.component.html` a
[name]="'::Author' | abpLocalization"
prop="authorName"
[sortable]="false"
->
+/>
````
When you run the application, you can see the *Author* column on the table:
@@ -1098,9 +1098,11 @@ Open the `/src/app/book/book.component.html` and add the following form group ju
*
````
diff --git a/docs/en/tutorials/microservice/index.md b/docs/en/tutorials/microservice/index.md
index 938d9b9108..7f6dc734f3 100644
--- a/docs/en/tutorials/microservice/index.md
+++ b/docs/en/tutorials/microservice/index.md
@@ -45,7 +45,7 @@ This tutorial is organized as the following parts:
## Download the Source Code
-After logging in to the ABP website, you can download the source code from {{if UI == "MVC"}} [here](https://abp.io/api/download/samples/cloud-crm-mvc-ef) {{else if UI == "NG"}} [here](https://abp.io/api/download/samples/cloud-crm-ng-ef) {{else if UI == "Blazor"}} [here](https://abp.io/api/download/samples/cloud-crm-blazor-wasm-ef) {{else if UI == "BlazorServer"}} [here](https://abp.io/api/download/samples/cloud-crm-blazor-server-ef) {{else if UI == "BlazorWebApp"}} [here](https://abp.io/api/download/samples/cloud-crm-blazor-webapp-ef) {{end}}.
+After logging in to the ABP website, you can download the source code from {{if UI == "MVC"}} [here](https://abp.io/api/download/samples/cloud-crm-mvc-ef) {{else if UI == "NG"}} [here](https://abp.io/api/download/samples/cloud-crm-angular-ef) {{else if UI == "Blazor"}} [here](https://abp.io/api/download/samples/cloud-crm-blazor-wasm-ef) {{else if UI == "BlazorServer"}} [here](https://abp.io/api/download/samples/cloud-crm-blazor-server-ef) {{else if UI == "BlazorWebApp"}} [here](https://abp.io/api/download/samples/cloud-crm-blazor-webapp-ef) {{end}}.
## See Also
diff --git a/docs/en/tutorials/microservice/part-01.md b/docs/en/tutorials/microservice/part-01.md
index a3529019a5..7006226e21 100644
--- a/docs/en/tutorials/microservice/part-01.md
+++ b/docs/en/tutorials/microservice/part-01.md
@@ -25,7 +25,7 @@
}
````
-Follow the *[Get Started](../../get-started/microservice.md)* guide to create a new layered web application with the following configurations:
+Follow the *[Get Started](../../get-started/microservice.md)* guide to create a new microservice solution with the following configurations:
* **Solution name**: `CloudCrm`
{{if DB == "EF"}}
@@ -82,4 +82,4 @@ You can see the *[Microservice Solution Template](../../solution-templates/micro
## Summary
-In this part, you've created the initial microservice solution, which already contains a few infrastructure services. We will create our first business service in the [next part](part-02.md).
\ No newline at end of file
+In this part, you've created the initial microservice solution, which already contains a few infrastructure services. We will create our first business service in the [next part](part-02.md).
diff --git a/docs/en/tutorials/microservice/part-05.md b/docs/en/tutorials/microservice/part-05.md
index 24da71a716..29727700e8 100644
--- a/docs/en/tutorials/microservice/part-05.md
+++ b/docs/en/tutorials/microservice/part-05.md
@@ -628,7 +628,7 @@ export const APP_ROUTES: Routes = [
// ...
{
path: 'order-service',
- children: ORDER_SERVICE_ROUTES,
+ loadChildren: () => import('ordering-service').then(c =>c.ORDER_SERVICE_ROUTES),
},
];
```
@@ -636,12 +636,8 @@ export const APP_ROUTES: Routes = [
```typescript
// order-service.routes.ts
export const ORDER_SERVICE_ROUTES: Routes = [
- {
- path: '',
- pathMatch: 'full',
- component: RouterOutletComponent,
- },
- { path: 'orders', children: ORDER_ROUTES },
+ { path: 'orders', loadComponent: () => import('./order/order.component').then(c => c.OrderComponent) },
+ { path: '**', redirectTo: 'orders' }
];
```
@@ -657,17 +653,16 @@ import { OrderDto, OrderService } from './proxy/ordering-service/services';
@Component({
selector: 'lib-order',
templateUrl: './order.component.html',
- styleUrl: './order.component.css'
+ styleUrl: './order.component.css',
imports: [CommonModule]
})
export class OrderComponent {
items: OrderDto[] = [];
-
- private readonly proxy = inject(OrderService);
+ private readonly orderService = inject(OrderService);
constructor() {
- this.proxy.getList().subscribe((res) => {
+ this.orderService.getList().subscribe((res) => {
this.items = res;
});
}
@@ -686,11 +681,13 @@ export class OrderComponent {
Product Id
Customer Name
-
-
{%{{{item.id}}}%}
-
{%{{{item.productId}}}%}
-
{%{{{item.customerName}}}%}
-
+ @for (item of items; track item.id) {
+
+
{%{{{item.id}}}%}
+
{%{{{item.productId}}}%}
+
{%{{{item.customerName}}}%}
+
+ }
diff --git a/docs/en/tutorials/microservice/part-06.md b/docs/en/tutorials/microservice/part-06.md
index bf54602936..a694631979 100644
--- a/docs/en/tutorials/microservice/part-06.md
+++ b/docs/en/tutorials/microservice/part-06.md
@@ -314,11 +314,13 @@ Open the `order.component.html` file (the `order.component.html` file under the
Product Name
Customer Name
-
-
{%{{{item.id}}}%}
-
{%{{{item.productName}}}%}
-
{%{{{item.customerName}}}%}
-
+ @for (item of items; track item.id) {
+
+
{%{{{item.id}}}%}
+
{%{{{item.productName}}}%}
+
{%{{{item.customerName}}}%}
+
+ }
diff --git a/docs/en/tutorials/mobile/index.md b/docs/en/tutorials/mobile/index.md
index 4a487f84bc..20767b9f1d 100644
--- a/docs/en/tutorials/mobile/index.md
+++ b/docs/en/tutorials/mobile/index.md
@@ -7,7 +7,7 @@
# Mobile Application Development Tutorial: Book Store Application
-> You must have an ABP Team or a higher license to be able to create a mobile application.
+> You must have an [ABP Team or a higher license](https://abp.io/pricing) to be able to create a mobile application.
Mobile application development tutorials are designed for developers who have completed [the web development part of the tutorial](../book-store/index.md) and wish to continue building the mobile version of the application.
diff --git a/docs/en/tutorials/mobile/maui/index.md b/docs/en/tutorials/mobile/maui/index.md
index fcd337f141..b1599021ba 100644
--- a/docs/en/tutorials/mobile/maui/index.md
+++ b/docs/en/tutorials/mobile/maui/index.md
@@ -9,7 +9,7 @@
## About This Tutorial
-> You must have an ABP Team or a higher license to be able to create a mobile application.
+> You must have an [ABP Team or a higher license](https://abp.io/pricing) to be able to create a mobile application.
This tutorial assumes that you have completed the [Web Application Development tutorial](../../book-store/part-01.md) and built an ABP based application named `Acme.BookStore` with [MAUI](../../../get-started/maui.md) as the mobile option. Therefore, if you haven't completed the [Web Application Development tutorial](../../book-store/part-01.md), you either need to complete it or download the source code from down below and follow this tutorial.
diff --git a/docs/en/tutorials/mobile/react-native/index.md b/docs/en/tutorials/mobile/react-native/index.md
index 5b43df18e6..3bfeb245c5 100644
--- a/docs/en/tutorials/mobile/react-native/index.md
+++ b/docs/en/tutorials/mobile/react-native/index.md
@@ -11,7 +11,7 @@ React Native mobile option is *available for* ***Team*** *or higher licenses*. T
## About This Tutorial
-> You must have an ABP Team or a higher license to be able to create a mobile application.
+> You must have an [ABP Team or a higher license](https://abp.io/pricing) to be able to create a mobile application.
- This tutorial assumes that you have completed the [Web Application Development tutorial](../../book-store/part-01.md) and built an ABP based application named `Acme.BookStore` with [React Native](../../../framework/ui/react-native) as the mobile option. Therefore, if you haven't completed the [Web Application Development tutorial](../../book-store/part-01.md), you either need to complete it or download the source code from down below and follow this tutorial.
- In this tutorial, we will only focus on the UI side of the `Acme.BookStore` application and will implement the CRUD operations.
diff --git a/docs/en/tutorials/todo/layered/index.md b/docs/en/tutorials/todo/layered/index.md
index 08c463e81c..c8d95b627c 100644
--- a/docs/en/tutorials/todo/layered/index.md
+++ b/docs/en/tutorials/todo/layered/index.md
@@ -59,7 +59,7 @@ This documentation has a video tutorial on **YouTube**!! You can watch it here:
## Pre-Requirements
-* An IDE (e.g. [Visual Studio](https://visualstudio.microsoft.com/vs/)) that supports [.NET 9.0+](https://dotnet.microsoft.com/download/dotnet) development.
+* An IDE (e.g. [Visual Studio](https://visualstudio.microsoft.com/vs/)) that supports [.NET 10.0+](https://dotnet.microsoft.com/download/dotnet) development.
* [Node v20.11+](https://nodejs.org/)
{{if DB=="EF"}}
* [SQL Server Express LocalDB](https://learn.microsoft.com/en-us/sql/database-engine/configure-windows/sql-server-express-localdb)
@@ -139,7 +139,7 @@ Ensure the `TodoApp.HttpApi.Host` project is the startup project, then run the a

-You can explore and test your HTTP API with this UI. Now, we can set the `TodoApp.Blazor` as the startup project and run it to open the actual Blazor application UI:
+You can explore and test your HTTP API with this UI. Now, we can set the {{if UI=="Blazor"}}`TodoApp.Blazor`{{else if UI=="MAUIBlazor"}}`TodoApp.MauiBlazor`{{end}} as the startup project and run it to open the actual Blazor application UI:
{{else if UI=="NG"}}
@@ -577,7 +577,11 @@ If you open the [Swagger UI](https://swagger.io/tools/swagger-ui/) by entering t
### Index.razor.cs
-Open the `Index.razor.cs` file in the `Pages` folder of the {{if UI=="Blazor" || UI=="BlazorWebApp"}} *TodoApp.Blazor.Client* {{else if UI=="BlazorServer"}} *TodoApp.Blazor* {{else if UI=="MAUIBlazor"}} *TodoApp.MauiBlazor* {{end}} project and replace the content with the following code block:
+Open the `Index.razor.cs` file in the `Pages` folder of the {{if UI=="Blazor" || UI=="BlazorWebApp"}} `TodoApp.Blazor.Client` {{else if UI=="BlazorServer"}} `TodoApp.Blazor` {{else if UI=="MAUIBlazor"}} `TodoApp.MauiBlazor` {{end}} project and replace the content with the following code block:
+
+{{if UI=="MAUIBlazor"}}
+_(Create this file if it doesn't exist)_
+{{end}}
```csharp
using Microsoft.AspNetCore.Components;
@@ -756,45 +760,46 @@ We can then use `todoService` to use the server-side HTTP APIs, as we'll do in t
Open the `/angular/src/app/home/home.component.ts` file and replace its content with the following code block:
-```js
+```ts
+import {Component, inject, OnInit} from '@angular/core';
+import {FormsModule} from '@angular/forms';
import { ToasterService } from '@abp/ng.theme.shared';
-import { Component, OnInit, inject } from '@angular/core';
import { TodoItemDto, TodoService } from '@proxy';
@Component({
- selector: 'app-home',
- standalone: false,
- templateUrl: './home.component.html',
- styleUrls: ['./home.component.scss']
+ selector: 'app-home',
+ templateUrl: './home.component.html',
+ styleUrls: ['./home.component.scss'],
+ imports: [FormsModule]
})
export class HomeComponent implements OnInit {
- todoItems: TodoItemDto[];
- newTodoText: string;
+ todoItems: TodoItemDto[];
+ newTodoText: string;
+ readonly todoService = inject(TodoService);
+ readonly toasterService = inject(ToasterService);
- private readonly todoService = inject(TodoService);
- private readonly toasterService = inject(ToasterService);
+ ngOnInit(): void {
+ this.todoService.getList().subscribe(response => {
+ this.todoItems = response;
+ });
+ }
- ngOnInit(): void {
- this.todoService.getList().subscribe(response => {
- this.todoItems = response;
- });
- }
-
- create(): void {
- this.todoService.create(this.newTodoText).subscribe((result) => {
- this.todoItems = this.todoItems.concat(result);
- this.newTodoText = null;
- });
- }
+ create(): void{
+ this.todoService.create(this.newTodoText).subscribe((result) => {
+ this.todoItems = this.todoItems.concat(result);
+ this.newTodoText = null;
+ });
+ }
- delete(id: string): void {
- this.todoService.delete(id).subscribe(() => {
- this.todoItems = this.todoItems.filter(item => item.id !== id);
- this.toasterService.info('Deleted the todo item.');
- });
- }
+ delete(id: string): void {
+ this.todoService.delete(id).subscribe(() => {
+ this.todoItems = this.todoItems.filter(item => item.id !== id);
+ this.toasterService.info('Deleted the todo item.');
+ });
+ }
}
+
```
We've used `todoService` to get the list of todo items and assigned the returning value to the `todoItems` array. We've also added `create` and `delete` methods. These methods will be used on the view side.
@@ -805,31 +810,35 @@ Open the `/angular/src/app/home/home.component.html` file and replace its conten
```html