Errors generating entities through ABP Suite #10484

8 Answer(s)

• 

  0

  AI-Bot created 17 hours ago

  Support Team ABP Agent

  • This compilation error happens when ABP Suite generates the customizable code pattern incorrectly (or it was partially generated), so the two files end up inheriting from each other:

    • PaymentsAppService.cs inherits from PaymentsAppServiceBase
    • and PaymentsAppServiceBase.cs inherits from PaymentsAppService

    That creates CS0146 Circular base type dependency, and because the base class can’t be compiled, you also see follow-up errors like “ObjectMapper does not exist in the current context” and interface members not implemented.

  • Fix (safe + minimal):

    1. Open PaymentsAppService.cs and PaymentsAppServiceBase.cs and make the inheritance one-way only:

       • PaymentsAppServiceBase must inherit from ABP’s ApplicationService (or CrudAppService<...> depending on what Suite generated).
       • PaymentsAppService must inherit from PaymentsAppServiceBase.
       • Ensure the base class does NOT inherit from the derived class.

       Example of the intended structure:

  // PaymentsAppServiceBase.cs
       public abstract class PaymentsAppServiceBase : ApplicationService, IPaymentsAppService
       {
           // generated implementations and protected helpers
       }
  
       // PaymentsAppService.cs
       public partial class PaymentsAppService : PaymentsAppServiceBase
       {
           // your customizations (can be empty)
       }
  

  2. After fixing inheritance, ensure PaymentsAppServiceBase ultimately derives from ApplicationService (directly or indirectly). That restores ObjectMapper (it’s provided by ApplicationService), and the interface implementation errors will disappear once the base class compiles.

  3. Clean + rebuild the solution.

  • Practical workaround if you want to avoid manual edits next time:
    • Regenerate the entity without “Preserve custom code / Customizable code” (so Suite generates a single app service file), or delete the generated PaymentsAppService*.cs files and regenerate again (so you don’t keep a broken partial generation state).

  No verified source available for this specific ABP Suite code-generation bug (the circular inheritance is a generated-code issue rather than a documented framework behavior).

  ---

  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.

  Save Cancel
• 

  0

  Prinay created 17 hours ago

  Fixing it manually defeats the purpose of the generation capability.

  I have unchecked "Customizable Code" - which is also disappointing - but still run into the error:

  

  Save Cancel
• 

  0

  AI-Bot created 17 hours ago

  Support Team ABP Agent

  • This is not caused by the “Customizable code” option at this point. The screenshot shows public class PaymentsAppService : PaymentsAppService, IPaymentsAppService — i.e., the class is inheriting from itself, which produces CS0146 (“Circular base type dependency involving 'PaymentsAppService' and 'PaymentsAppService'”).
  • When the AppService class fails to compile, you also get secondary errors like ObjectMapper does not exist (because the generated class no longer successfully derives from ApplicationService).

  Solution

  1. Delete the previously generated Payment service artifacts (so Suite doesn’t try to merge into a broken state):
     • In Payments.Application, delete:
       • PaymentsAppService.cs
       • Any related generated partial/base files for payments (e.g., PaymentsAppServiceBase.cs, PaymentsAppService.Extended.cs, etc. if they exist)
     • Also delete the generated payments DTO folder/files and application contract interface if they were partially generated (only those related to Payment).
  2. Clean the solution output folders:
     • Delete all bin/obj folders (or run dotnet clean).
  3. Regenerate the entity again from ABP Suite (with Customizable Code on or off—either is fine once you’ve removed the corrupted generated files).
  4. If it still generates : PaymentsAppService (self-inheritance), this indicates a code-generation bug in ABP Suite 10.1.0 for your project state. The only non-manual workaround is:
     • Upgrade ABP Suite / ABP Studio to a newer patch version (so the generator is fixed), then regenerate.

  Why generation fails at “DB migration step”

  ABP Suite runs a build before migrations. Since the generated code has self-inheritance, build fails, so Suite stops and shows the “Make sure the project is compiled and working” dialog.

  Verified external reference (related known .NET DI circular issues; not the same as your compile-time issue)

  • https://www.nuget.org/packages/Microsoft.Extensions.Caching.StackExchangeRedis/9.0.5

  No verified source available for this specific ABP Suite self-inheriting AppService generation issue.

  ---

  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.

  Save Cancel
• 

  0

  Prinay created 16 hours ago

  I have deleted all generated code and reran generation from ABP suite but still experience the error. I have also tried switching to the preview version 10.2.0-rc.1 for the abp project and for ABP studio but the error still persist.

  Save Cancel
• 

  0

  Prinay created 15 hours ago

  Additional context. If I create related entities with Create user interfaces checked I run into even more issues. Again, I have made 0 customisations and this is just pure generation at this point.

  Save Cancel
• 

  0

  EngincanV created 15 hours ago

  Support Team .NET Developer

  [Prinay] said: Additional context.

  If I create related entities with Create user interfaces checked I run into even more issues.

  

  Again, I have made 0 customisations and this is just pure generation at this point.

  Hi Prinay,

  It seems the error is caused by the project name and entity name being the same. To help us reproduce the issue, could you share your solution via email to support@abp.io with your ticket number? If that's not possible, please let me know and I'll try to reproduce it using the configurations you've provided above.

  Also, could you confirm whether you have a DTO class called DownloadTokenResultDto and that its namespace is different from Payments.Shared?

  Best regards.

  Save Cancel
• 

  0

  Prinay created 11 hours ago

  Hi EngincanV,

  Your recommendation worked perfectly. I have renamed the entity to not match the project name and it generated perfectly. I will note this going forward. The DownloadTokenResultDto error is also gone. I suspect it was the conflicting namespace too as you mentioned. Thanks for the assistance.

  Save Cancel
• 

  0

  EngincanV created 11 hours ago

  Support Team .NET Developer

  [Prinay] said: Hi EngincanV,

  Your recommendation worked perfectly. I have renamed the entity to not match the project name and it generated perfectly.

  I will note this going forward. The DownloadTokenResultDto error is also gone. I suspect it was the conflicting namespace too as you mentioned.

  Thanks for the assistance.

  Hi @Prinay, I'm happy to help.

  Best regards.

  Save Cancel