Open Closed

Make sure ABP Suite version is equal to the `Volo.Abp.Commercial.SuiteTemplates` package version and that your solution has been built recently. The template below is missing: Volo.Abp.Commercial.SuiteTemplates.Templates.Server.ObjectMapping.ApplicationMap #10569

User avatar
0
consultant.ahmet.ulusoy created

Dear Abp Team,

After we migrate v9.3.6 to 10.2.0 in our microservice solution we can't generate code with abp suite.

It's giving below error.

Make sure ABP Suite version is equal to the Volo.Abp.Commercial.SuiteTemplates package version and that your solution has been built recently. The template below is missing: Volo.Abp.Commercial.SuiteTemplates.Templates.Server.ObjectMapping.ApplicationMapperlyMapper_Usings.txt

We have an object mapper cs file unde ObjectMapping folder with "SettingServiceApplicationMappers" name.

Can you help us, please?

Markdown supported.
Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)
Go to accepted answer
10 Answer(s)
  • User Avatar
    0
    AI-Bot created
    Support Team ABP Agent
    • This error is thrown by ABP Suite when it can’t find/read the embedded template resources from the same version of Volo.Abp.Commercial.SuiteTemplates that matches your installed ABP Suite version, or when your solution output still contains old assemblies (common after upgrading from 9.x to 10.x).

    Do the following in order (this fully fixes the “template missing …ApplicationMapperlyMapper_Usings.txt” class of errors):

    1. Make ABP Suite version match your solution (10.2.x)

      • If you are running Suite from ABP Studio, use the “change version”/version matching UI so Suite matches the solution’s ABP version.
      • If you run Suite standalone, update/downgrade Suite so it is exactly compatible with ABP 10.2.0.

    2. Ensure Volo.Abp.Commercial.SuiteTemplates version matches the Suite version

      • In your solution, locate all references to Volo.Abp.Commercial.SuiteTemplates and make sure the version is exactly the same as the ABP Suite version you’re running (not just “10.x”, but the exact patch line).
      • Restore packages.

    3. Hard clean the solution outputs (removes stale 9.x assemblies)

      • Close Visual Studio/Rider (important).
      • Delete all bin and obj folders under the entire solution (all microservices and shared projects).
      • Reopen the solution.

    4. Build the solution (Suite requires a recent build)

      • Build the whole solution (or at least the target service you generate code for).
      • Then restart ABP Suite and try generation again.

    5. If you migrated to Mapperly: keep Suite-managed mapper files “clean”

      • Since your error references ApplicationMapperly..., you are on the Mapperly path. Keep the conventional, Suite-managed files in ObjectMapping (like *ApplicationMappers.cs) reserved for Suite updates.
      • Put your manual mappings in separate files with different naming so Suite doesn’t pick the wrong file.

    This is why having an ObjectMapping/SettingServiceApplicationMappers file is fine, but if there are extra/misnamed files or stale builds, Suite may not resolve the expected template-to-file conventions correctly.

    Links (verified):

    • https://abp.io/docs/10.2/suite/editing-templates
    • https://abp.io/docs/10.2/studio/working-with-suite
    • https://abp.io/docs/10.2/release-info/migration-guides/AutoMapper-To-Mapperly

    This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.

    Markdown supported.
    Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)
  • User Avatar
    0
    consultant.ahmet.ulusoy created

    When i try to do that it says.

    Unable to fetch the versions of ABP Suite. Error: Unable to load the service index for source https://pkgs.dev.azure.com/treva-marketplace-platform/_packaging/TavTechnologies.Treva/nuget/v3/index.json .

    Markdown supported.
    Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)
  • User Avatar
    0
    AI-Bot created
    Support Team ABP Agent

    • ABP Studio / Suite is trying to query available Suite versions via NuGet, but on your machine NuGet restore is configured with a feed that is currently unreachable:

      https://pkgs.dev.azure.com/treva-marketplace-platform/_packaging/TavTechnologies.Treva/nuget/v3/index.json

      When that feed is down / blocked (VPN, proxy, credentials), NuGet operations fail, and Studio can’t fetch the version list.

    Do this:

    1. Fix or disable the failing NuGet source

      • Open your NuGet sources (global/user level) and disable that Azure DevOps feed or fix its connectivity/credentials.
      • Typical places to check:
        • %AppData%\NuGet\NuGet.Config (Windows user-level)
        • NuGet.Config in your solution / repo (if you have one)
        • Any environment-managed config your company uses
      • After disabling/fixing it, retry “fetch versions” in Studio.

    2. Workaround: install the Suite version explicitly (no “fetch versions” UI needed) Run this in a terminal (same user that runs Studio/Suite):

    abp suite install --version 10.2.0
   # or update to an explicit version
   abp suite update --version 10.2.0

    Then run:

    abp suite
    1. If Suite also uses ABP account/license and you see authentication-related problems Re-login with ABP CLI:
    abp logout
   abp login
    1. After you can manage Suite versions again, go back to your original issue and ensure:
      • Suite version == Volo.Abp.Commercial.SuiteTemplates version
      • delete all bin/obj and rebuild the solution

    (Verified)

    • https://abp.io/docs/10.2/suite/how-to-install
    • https://abp.io/support/questions/3757

    This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.

    Markdown supported.
    Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)
  • User Avatar
    0
    consultant.ahmet.ulusoy created

    No change

    Markdown supported.
    Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)
  • User Avatar
    0
    AI-Bot created
    Support Team ABP Agent
    • The “Unable to fetch the versions of ABP Suite” problem is not ABP Suite itself; it’s your machine’s NuGet configuration. ABP Studio/Suite internally executes NuGet operations, and if any configured NuGet feed is unreachable, NuGet can fail with:

    Unable to load the service index for source .../nuget/v3/index.json

    So the fix is to make NuGet not use that unreachable Azure DevOps feed for Studio/Suite operations.

    1) Fix the NuGet feed that is breaking Studio/Suite

    Disable or remove this source from NuGet config:

    https://pkgs.dev.azure.com/treva-marketplace-platform/_packaging/TavTechnologies.Treva/nuget/v3/index.json

    Where to do it (do all that apply):

    A. Global/user NuGet.Config

    • Windows: %AppData%\NuGet\NuGet.Config
    • Also check machine-wide configs:
      • C:\Program Files (x86)\NuGet\Config\*.config
      • C:\ProgramData\NuGet\Config\*.config

    B. Repo-level NuGet.Config

    • Search your solution folder for NuGet.Config and check if that feed is defined there too.

    C. Visual Studio NuGet sources

    • VS: Tools → NuGet Package Manager → Package Manager Settings → Package Sources
    • Disable that source there as well (VS writes to config).

    After disabling/removing it, run in a terminal:

    dotnet nuget list source
dotnet nuget locals all --clear

    Restart ABP Studio and try “fetch versions” again.

    2) If you must keep that private feed, isolate ABP Studio from it

    Create a NuGet.Config that only contains public sources (nuget.org) and make Studio/CLI use it.

    Example minimal config (save somewhere like C:\Temp\abp-nuget-only-nugetorg.config):

    <?xml version="1.0" encoding="utf-8"?>
<configuration>
  <packageSources>
    <clear />
    <add key="nuget.org" value="https://api.nuget.org/v3/index.json" />
  </packageSources>
</configuration>

    Then use that config when you install/update the Studio CLI (the part that typically fails when feeds are broken):

    dotnet tool update -g Volo.Abp.Studio.Cli --configfile C:\Temp\abp-nuget-only-nugetorg.config

    Once Studio can successfully manage its CLI and version mapping, you can return to the original “SuiteTemplates template missing” issue (version mismatch / stale build outputs).

    3) Verified reference of the same root cause (broken private feed in global NuGet.Config)

    This is the same pattern as an ABP Studio CLI install failure caused by an unreachable company NuGet feed; removing it fixed the issue:

    • https://abp.io/support/questions/8950

    Sources

    • https://abp.io/support/questions/8950
    • https://learn.microsoft.com/en-us/nuget/consume-packages/configuring-nuget-behavior#nugetdefaultsconfig-location
    • https://www.nuget.org/packages/Volo.Abp.Studio.Cli
    • https://abp.io/docs/10.2/studio/version-mapping
    • https://abp.io/docs/10.2/studio/installation

    This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.

    Markdown supported.
    Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)
  • User Avatar
    0
    consultant.ahmet.ulusoy created

    2026-04-07 12:08:28.335 +03:00 [INF] 1/12 - EnumGenerateCommand started... 2026-04-07 12:08:28.353 +03:00 [INF] 1/12 - EnumGenerateCommand completed. | Duration: 11 ms. 2026-04-07 12:08:28.353 +03:00 [INF] 2/12 - EntityGenerateCommand started... 2026-04-07 12:08:28.373 +03:00 [INF] Request starting HTTP/1.1 GET http://localhost:3000/Themes/Lepton/Global/assets/fonts/poppins-v6-latin-700.woff2 - null null 2026-04-07 12:08:28.373 +03:00 [INF] Sending file. Request path: '/Themes/Lepton/Global/assets/fonts/poppins-v6-latin-700.woff2'. Physical path: 'N/A' 2026-04-07 12:08:28.374 +03:00 [INF] Request finished HTTP/1.1 GET http://localhost:3000/Themes/Lepton/Global/assets/fonts/poppins-v6-latin-700.woff2 - 200 7924 font/woff2 0.4315ms 2026-04-07 12:08:30.748 +03:00 [INF] 2/12 - EntityGenerateCommand completed. | Duration: 2394 ms. 2026-04-07 12:08:30.749 +03:00 [INF] 3/12 - RepositoryCommand started... 2026-04-07 12:08:32.634 +03:00 [INF] 3/12 - RepositoryCommand completed. | Duration: 1885 ms. 2026-04-07 12:08:32.634 +03:00 [INF] 4/12 - ManagerCommand started... 2026-04-07 12:08:33.335 +03:00 [INF] 4/12 - ManagerCommand completed. | Duration: 700 ms. 2026-04-07 12:08:33.335 +03:00 [INF] 5/12 - AppServiceCommand started... 2026-04-07 12:08:43.564 +03:00 [INF] 5/12 - AppServiceCommand completed. | Duration: 10229 ms. 2026-04-07 12:08:43.565 +03:00 [INF] 6/12 - PermissionCommand started... 2026-04-07 12:08:43.953 +03:00 [INF] 6/12 - PermissionCommand completed. | Duration: 388 ms. 2026-04-07 12:08:43.953 +03:00 [INF] 7/12 - ApplicationObjectMappingCommand started... 2026-04-07 12:08:44.052 +03:00 [WRN] ---------- RemoteServiceErrorInfo ---------- { "code": null, "message": "Make sure ABP Suite version is equal to the Volo.Abp.Commercial.SuiteTemplates package version and that your solution has been built recently. The template below is missing: Volo.Abp.Commercial.SuiteTemplates.Templates.Server.ObjectMapping.ApplicationMapperlyMapper_Usings.txt", "details": null, "data": {}, "validationErrors": null }

    2026-04-07 12:08:44.052 +03:00 [WRN] Make sure ABP Suite version is equal to the Volo.Abp.Commercial.SuiteTemplates package version and that your solution has been built recently. The template below is missing: Volo.Abp.Commercial.SuiteTemplates.Templates.Server.ObjectMapping.ApplicationMapperlyMapper_Usings.txt Volo.Abp.UserFriendlyException: Make sure ABP Suite version is equal to the Volo.Abp.Commercial.SuiteTemplates package version and that your solution has been built recently. The template below is missing: Volo.Abp.Commercial.SuiteTemplates.Templates.Server.ObjectMapping.ApplicationMapperlyMapper_Usings.txt at Volo.Abp.Suite.Areas.AbpSuite.CrudPageGenerator.Services.TemplateService.ReadFromTemplateAsync(String relativeResourceName, CrudPageCommandOptions options, String defaultValue) at Volo.Abp.Suite.Areas.AbpSuite.CrudPageGenerator.Services.TemplateService.PopulateTemplateAsync(String relativeResourceName, CrudPageCommandOptions options) at Volo.Abp.Suite.Areas.AbpSuite.CrudPageGenerator.Commands.Mappings.ApplicationObjectMappingGeneratorBase.AddUsingStatementsAsync(String templateName, String content, CrudPageCommandOptions options) at Volo.Abp.Suite.Areas.AbpSuite.CrudPageGenerator.Commands.Mappings.ApplicationMapperlyMappingGenerator.GenerateMappingsAsync(CrudPageCommandOptions options) at Volo.Abp.Suite.Areas.AbpSuite.CrudPageGenerator.Commands.Mappings.ApplicationObjectMappingGeneratorBase.GenerateAsync(CrudPageCommandOptions options) at Volo.Abp.Suite.Areas.AbpSuite.CrudPageGenerator.Commands.ApplicationObjectMappingCommand.ExecuteAsync(CrudPageCommandOptions options) at Volo.Abp.Suite.Areas.AbpSuite.CrudPageGenerator.CommandManager.ExecuteAllAsync(CrudPageCommandOptions options) at Volo.Abp.Suite.Areas.AbpSuite.CrudPageGenerator.Commands.CrudPageGenerator.GenerateAsync(EntityModel entity, Solution solution, EntityModel masterEntity, List1 navigationConnections) at Volo.Abp.Suite.Controllers.CrudPageGeneratorController.SaveAndGenerateEntityAsync(Guid solutionId, EntityModel entity) at lambda_method1926(Closure, Object) at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.TaskOfActionResultExecutor.Execute(ActionContext actionContext, IActionResultTypeMapper mapper, ObjectMethodExecutor executor, Object controller, Object[] arguments) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.<InvokeActionMethodAsync>g__Awaited|12_0(ControllerActionInvoker invoker, ValueTask1 actionResultValueTask) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.<InvokeNextActionFilterAsync>g__Awaited|10_0(ControllerActionInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Rethrow(ActionExecutedContextSealed context) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.<InvokeInnerFilterAsync>g__Awaited|13_0(ControllerActionInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted) at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeNextExceptionFilterAsync>g__Awaited|26_0(ResourceInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted) 2026-04-07 12:08:44.098 +03:00 [INF] Executing ObjectResult, writing value of type 'Volo.Abp.Http.RemoteServiceErrorResponse'. 2026-04-07 12:08:44.100 +03:00 [INF] Executed action Volo.Abp.Suite.Controllers.CrudPageGeneratorController.SaveAndGenerateEntityAsync (Volo.Abp.Suite) in 16585.1561ms 2026-04-07 12:08:44.100 +03:00 [INF] Executed endpoint 'Volo.Abp.Suite.Controllers.CrudPageGeneratorController.SaveAndGenerateEntityAsync (Volo.Abp.Suite)' 2026-04-07 12:08:44.100 +03:00 [INF] Request finished HTTP/1.1 POST http://localhost:3000/api/abpSuite/crudPageGenerator/c06e49a2-2650-4930-8902-4e9ec28c033b/save-and-generate-entity - 403 null application/json; charset=utf-8 16590.798ms 2026-04-07 12:08:49.986 +03:00 [INF] Request starting HTTP/1.1 GET http://localhost:3000/api/abpSuite/open-logs-folder - application/json null 2026-04-07 12:08:49.986 +03:00 [INF] Executing endpoint 'Volo.Abp.Suite.Controllers.AbpSuiteController.OpenLogsFolder (Volo.Abp.Suite)' 2026-04-07 12:08:49.987 +03:00 [INF] Route matched with {action = "OpenLogsFolder", controller = "AbpSuite", area = "", page = ""}. Executing controller action with signature Void OpenLogsFolder() on controller Volo.Abp.Suite.Controllers.AbpSuiteController (Volo.Abp.Suite). 2026-04-07 12:08:50.398 +03:00 [INF] Executed action Volo.Abp.Suite.Controllers.AbpSuiteController.OpenLogsFolder (Volo.Abp.Suite) in 410.8156ms 2026-04-07 12:08:50.398 +03:00 [INF] Executed endpoint 'Volo.Abp.Suite.Controllers.AbpSuiteController.OpenLogsFolder (Volo.Abp.Suite)' 2026-04-07 12:08:50.398 +03:00 [INF] Request finished HTTP/1.1 GET http://localhost:3000/api/abpSuite/open-logs-folder - 204 null null 412.1378ms

    Markdown supported.
    Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)
  • User Avatar
    0
    AI-Bot created
    Support Team ABP Agent
    • Your log shows ABP Suite starts generating normally and fails at 7/12 – ApplicationObjectMappingCommand, when it tries to read this embedded template resource:

    Volo.Abp.Commercial.SuiteTemplates.Templates.Server.ObjectMapping.ApplicationMapperlyMapper_Usings.txt

    That file exists only in the SuiteTemplates package version that matches the Suite version. If Suite is running a different version (or it is loading an older Volo.Abp.Commercial.SuiteTemplates.dll from stale build output), it will throw exactly this “template missing” exception.

    Do this fixed sequence (works even when Studio can’t “fetch versions” because of your private NuGet feed):

    1. Force Suite to use the correct version (10.2.x) without the “fetch versions” UI

      • Close ABP Studio + ABP Suite.
      • Open a terminal and run ABP Suite directly for the installed version you want (10.2.x). If you have multiple installed, remove the others and keep only 10.2.x.

      If you are using the Studio-managed Suite installation, uninstall all installed Suite versions from Studio (or delete the local installed Suite folders) and then install again after you fix NuGet feeds (step 2). The key is: only one Suite version should remain, matching 10.2.x.

    2. Fix the NuGet feed issue so Studio/Suite can actually install/resolve matching packages

      • The error about https://pkgs.dev.azure.com/.../index.json means your machine has a NuGet source that is unreachable and it breaks NuGet operations.
      • Disable that feed in all NuGet.Config layers that affect the user running Studio:
        • %AppData%\NuGet\NuGet.Config
        • Any NuGet.Config under the repository
        • Visual Studio NuGet Package Sources (if applicable)

      Then clear NuGet caches:

    dotnet nuget locals all --clear

    1. Ensure Volo.Abp.Commercial.SuiteTemplates package version exactly matches Suite

      • In the microservice where you generate CRUD, verify the package reference version is exactly aligned with your Suite version (same major/minor/patch line).
      • Restore packages.

    2. Eliminate stale 9.x / older SuiteTemplates assemblies (most common cause after upgrades)

      • Close IDE.
      • Delete all bin and obj folders for the entire solution (every microservice + shared projects).
      • Rebuild the whole solution.
      • Start Suite again and retry generation.

    3. Mapperly-specific note (avoid naming collisions in ObjectMapping)

      • Since Suite is using the Mapperly templates (your error contains ApplicationMapperly...), keep Suite-managed conventional mapper files reserved for Suite:
        • *ApplicationMappers.cs, *BlazorMappers.cs, *WebMappers.cs
      • Put your manual mappings into differently named files (do not create extra files that end with those conventional suffixes), otherwise Suite may edit/scan the wrong file.

    Links (validated):

    • https://abp.io/docs/10.2/suite/editing-templates
    • https://abp.io/docs/10.2/studio/working-with-suite
    • https://abp.io/docs/10.2/release-info/migration-guides/AutoMapper-To-Mapperly
    • https://abp.io/support/questions/671

    This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.

    Markdown supported.
    Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)
  • User Avatar
    0
    consultant.ahmet.ulusoy created

    I did all of the steps but logs like same as before

    2026-04-07 12:14:43.794 +03:00 [INF] 1/12 - EnumGenerateCommand started... 2026-04-07 12:14:43.814 +03:00 [INF] 1/12 - EnumGenerateCommand completed. | Duration: 13 ms. 2026-04-07 12:14:43.815 +03:00 [INF] 2/12 - EntityGenerateCommand started... 2026-04-07 12:14:46.391 +03:00 [INF] 2/12 - EntityGenerateCommand completed. | Duration: 2576 ms. 2026-04-07 12:14:46.391 +03:00 [INF] 3/12 - RepositoryCommand started... 2026-04-07 12:14:48.246 +03:00 [INF] 3/12 - RepositoryCommand completed. | Duration: 1854 ms. 2026-04-07 12:14:48.246 +03:00 [INF] 4/12 - ManagerCommand started... 2026-04-07 12:14:48.932 +03:00 [INF] 4/12 - ManagerCommand completed. | Duration: 686 ms. 2026-04-07 12:14:48.932 +03:00 [INF] 5/12 - AppServiceCommand started... 2026-04-07 12:14:58.157 +03:00 [INF] 5/12 - AppServiceCommand completed. | Duration: 9224 ms. 2026-04-07 12:14:58.157 +03:00 [INF] 6/12 - PermissionCommand started... 2026-04-07 12:14:58.521 +03:00 [INF] 6/12 - PermissionCommand completed. | Duration: 363 ms. 2026-04-07 12:14:58.521 +03:00 [INF] 7/12 - ApplicationObjectMappingCommand started... 2026-04-07 12:14:58.607 +03:00 [WRN] ---------- RemoteServiceErrorInfo ---------- { "code": null, "message": "Make sure ABP Suite version is equal to the Volo.Abp.Commercial.SuiteTemplates package version and that your solution has been built recently. The template below is missing: Volo.Abp.Commercial.SuiteTemplates.Templates.Server.ObjectMapping.ApplicationMapperlyMapper_Usings.txt", "details": null, "data": {}, "validationErrors": null }

    2026-04-07 12:14:58.607 +03:00 [WRN] Make sure ABP Suite version is equal to the Volo.Abp.Commercial.SuiteTemplates package version and that your solution has been built recently. The template below is missing: Volo.Abp.Commercial.SuiteTemplates.Templates.Server.ObjectMapping.ApplicationMapperlyMapper_Usings.txt Volo.Abp.UserFriendlyException: Make sure ABP Suite version is equal to the Volo.Abp.Commercial.SuiteTemplates package version and that your solution has been built recently. The template below is missing: Volo.Abp.Commercial.SuiteTemplates.Templates.Server.ObjectMapping.ApplicationMapperlyMapper_Usings.txt at Volo.Abp.Suite.Areas.AbpSuite.CrudPageGenerator.Services.TemplateService.ReadFromTemplateAsync(String relativeResourceName, CrudPageCommandOptions options, String defaultValue) at Volo.Abp.Suite.Areas.AbpSuite.CrudPageGenerator.Services.TemplateService.PopulateTemplateAsync(String relativeResourceName, CrudPageCommandOptions options) at Volo.Abp.Suite.Areas.AbpSuite.CrudPageGenerator.Commands.Mappings.ApplicationObjectMappingGeneratorBase.AddUsingStatementsAsync(String templateName, String content, CrudPageCommandOptions options) at Volo.Abp.Suite.Areas.AbpSuite.CrudPageGenerator.Commands.Mappings.ApplicationMapperlyMappingGenerator.GenerateMappingsAsync(CrudPageCommandOptions options) at Volo.Abp.Suite.Areas.AbpSuite.CrudPageGenerator.Commands.Mappings.ApplicationObjectMappingGeneratorBase.GenerateAsync(CrudPageCommandOptions options) at Volo.Abp.Suite.Areas.AbpSuite.CrudPageGenerator.Commands.ApplicationObjectMappingCommand.ExecuteAsync(CrudPageCommandOptions options) at Volo.Abp.Suite.Areas.AbpSuite.CrudPageGenerator.CommandManager.ExecuteAllAsync(CrudPageCommandOptions options) at Volo.Abp.Suite.Areas.AbpSuite.CrudPageGenerator.Commands.CrudPageGenerator.GenerateAsync(EntityModel entity, Solution solution, EntityModel masterEntity, List1 navigationConnections) at Volo.Abp.Suite.Controllers.CrudPageGeneratorController.SaveAndGenerateEntityAsync(Guid solutionId, EntityModel entity) at lambda_method1944(Closure, Object) at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.TaskOfActionResultExecutor.Execute(ActionContext actionContext, IActionResultTypeMapper mapper, ObjectMethodExecutor executor, Object controller, Object[] arguments) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.<InvokeActionMethodAsync>g__Awaited|12_0(ControllerActionInvoker invoker, ValueTask1 actionResultValueTask) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.<InvokeNextActionFilterAsync>g__Awaited|10_0(ControllerActionInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Rethrow(ActionExecutedContextSealed context) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.<InvokeInnerFilterAsync>g__Awaited|13_0(ControllerActionInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted) at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeNextExceptionFilterAsync>g__Awaited|26_0(ResourceInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted) 2026-04-07 12:14:58.637 +03:00 [INF] Executing ObjectResult, writing value of type 'Volo.Abp.Http.RemoteServiceErrorResponse'. 2026-04-07 12:14:58.638 +03:00 [INF] Executed action Volo.Abp.Suite.Controllers.CrudPageGeneratorController.SaveAndGenerateEntityAsync (Volo.Abp.Suite) in 15662.5308ms 2026-04-07 12:14:58.638 +03:00 [INF] Executed endpoint 'Volo.Abp.Suite.Controllers.CrudPageGeneratorController.SaveAndGenerateEntityAsync (Volo.Abp.Suite)' 2026-04-07 12:14:58.638 +03:00 [INF] Request finished HTTP/1.1 POST http://localhost:3000/api/abpSuite/crudPageGenerator/c06e49a2-2650-4930-8902-4e9ec28c033b/save-and-generate-entity - 403 null application/json; charset=utf-8 15668.3583ms

    Markdown supported.
    Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)
  • User Avatar
    0
    AI-Bot created
    Support Team ABP Agent
    • The stack trace proves Suite is failing inside its own template reader (TemplateService.ReadFromTemplateAsync) because it cannot find the embedded resource ApplicationMapperlyMapper_Usings.txt in the Volo.Abp.Commercial.SuiteTemplates assembly it has loaded.

    If you already cleaned bin/obj and rebuilt and it still happens, then one of these is true:

    1. Suite is not actually running the 10.2.x engine (you still have an older/newer Suite installed and Studio is launching that one), or
    2. Your solution is restoring a different Volo.Abp.Commercial.SuiteTemplates version than the one Suite expects (often because Central Package Management / Directory.Packages.props / a pinned version somewhere), or
    3. The build that Suite is using is not the one you think (wrong solution selected in Suite, wrong service selected, or multiple outputs).

    Do the following “hard verification” steps (no guesswork):

    1) Verify the actual Volo.Abp.Commercial.SuiteTemplates version resolved by your solution

    In the same project where you generate CRUD (typically the *.HttpApi.Host or the related app project), run:

    dotnet list <YourProject>.csproj package --include-transitive | findstr /i "Volo.Abp.Commercial.SuiteTemplates"

    Then force it to the exact version you want (10.2.0 or whatever patch you use) by updating the place where you centrally manage versions:

    • Directory.Packages.props (Central Package Management), or
    • any Directory.Build.props, or
    • direct <PackageReference ... Version="...">

    After that:

    dotnet restore

    2) Ensure ABP Suite and SuiteTemplates are the same version (and that Studio is launching that version)

    ABP Studio supports automatic version matching, but in your environment it previously failed to fetch versions due to the broken Azure DevOps feed. So you must manually ensure only one Suite version is installed and it matches your solution.

    Do this:

    • Close Studio.
    • Remove old installed Suite versions from the Studio/Suite installation location (leave only the one matching your solution ABP version).
    • Start Suite again and re-open the solution.

    (Reason: if multiple versions exist, Studio may launch a different installed one even if your solution is 10.2.0.)

    3) Clean NuGet caches (stale SuiteTemplates DLL can survive even if you delete bin/obj)

    Delete bin/obj is not always enough if the wrong SuiteTemplates version is coming from global cache.

    Run:

    dotnet nuget locals all --clear

    Then restore + rebuild again:

    dotnet restore
dotnet build

    4) Mapperly migration collision check (prevents Suite from updating expected mapper files)

    Since the missing template is Mapperly-specific, ensure you didn’t create extra files that match Suite’s conventional mapper file naming.

    Make sure you have only one Suite-managed application mapper file for that service, typically:

    • *ApplicationMappers.cs

    Move your custom mapper code to differently named files (do not use the same *ApplicationMappers.cs suffix).

    Sources (validated)

    • https://abp.io/docs/10.2/suite/editing-templates (templates are embedded in Volo.Abp.Commercial.SuiteTemplates and must match Suite version)
    • https://abp.io/docs/10.2/studio/working-with-suite (Studio runs Suite with version matching)
    • https://abp.io/support/questions/671 (classic “Cannot read template” fix: version mismatch and stale outputs)
    • https://abp.io/docs/10.2/release-info/migration-guides/AutoMapper-To-Mapperly (Suite + Mapperly naming guidance)
    • https://abp.io/docs/10.2/suite/generating-crud-page (troubleshooting after Mapperly migration)

    If you apply steps (1) and (2) exactly, this error disappears because Suite will load the SuiteTemplates assembly that actually contains ApplicationMapperlyMapper_Usings.txt.

    This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.

    Markdown supported.
    Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)
  • User Avatar
    1
    EngincanV created
    Support Team .NET Developer

    Hi @consultant.ahmet.ulusoy, we have added a new code template file called ApplicationMapperlyMapper_Usings.txt to support our new Mapperly mapping code generations with v10.0.0-rc.1. So, the Volo.Abp.Commercial.SuiteTemplates NuGet package version on your *Domain project should be v10.0.0-rc.1+. And, from the error message, as specified, it seems it's version seems lower than this version.

    So, can you please confirm that the relevant NuGet package version is indeed v10.0.0-rc.1+ and you have rebuilt your solution?

    If you confirm this I can help you further, and as a next step, I can provide you its content and we can add it to your local folder to suprass the error like the file is already exists in your project. (This is a quick workaround, but without needing that it should work as expected. After this workaround, we may need to do additional fixes on your setup, so waiting for your confirmation...)

    Best regards.

    Markdown supported.
    Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)
Assignee
User avatar EngincanV
Question details
Labels
None yet
Boost Your Development
ABP Live Training
Packages
See Trainings
Mastering ABP Framework Book
The Official Guide
Mastering
ABP Framework
Learn More
Mastering ABP Framework Book
Made with ❤️ on ABP v10.8.0-preview. Updated on September 09, 2026, 11:56
1
ABP Assistant
🔐 You need to be logged in to use the chatbot. Please log in first.