From 19572e405601088e565f1cade0cf09c580812276 Mon Sep 17 00:00:00 2001 From: pyrokin5 <30674383+pyrokin5@users.noreply.github.com> Date: Tue, 16 Sep 2025 14:52:48 -0400 Subject: [PATCH] Update plugin modules documentation for clarity --- .../framework/architecture/modularity/plugin-modules.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/en/framework/architecture/modularity/plugin-modules.md b/docs/en/framework/architecture/modularity/plugin-modules.md index c4c7c51d04..ce9e64f655 100644 --- a/docs/en/framework/architecture/modularity/plugin-modules.md +++ b/docs/en/framework/architecture/modularity/plugin-modules.md @@ -1,6 +1,6 @@ # Plug-In Modules -It is possible to load [modules](../modularity/basics.md) as plug-ins. That means you may not reference to a module's assembly in your solution, but you can load that module in the application startup just like any other module. +[Modules](../modularity/basics.md) can also be loaded as plug-ins. This means that you don’t need to reference a module’s assembly directly in your solution; instead, you can load it during application startup in the same way as any other module. ## Basic Usage @@ -28,7 +28,7 @@ That's all. ABP will discover the modules in the given folder, configure and ini options.PlugInSources.Add(new FolderPlugInSource(@"D:\Temp\MyPlugIns")); ```` -> `AddFolder()` only looks for the assembly file in the given folder, but not looks for the sub-folders. You can pass `SearchOption.AllDirectories` as a second parameter to explore plug-ins also from the sub-folders, recursively. +> `AddFolder()` only looks for the assembly file in the given folder, but doesn't look for the sub-folders. You can pass `SearchOption.AllDirectories` as a second parameter to explore plug-ins also from the sub-folders, recursively. There are two more built-in Plug-In Source implementations: @@ -124,13 +124,13 @@ Edit the `.csproj` file content: - net5.0 + net9.0 Library true - +