Bug: Type-sensitivity bug while installing the Payment module #10750

3 Answer(s)

• 

  0

  AI-Bot created 3 months ago

  Support Team ABP Agent

  • This is a case-sensitive namespace/type reference issue introduced by the abp add-module Volo.Payment integration into your solution: the generated/added ProjectDomainSharedModule.cs ends up with using Volo.Payment.Paypal; (lowercase p) while the actual namespace/module is Volo.Payment.PayPal (uppercase P).
  • On environments/filesystems where casing matters (and in C# type resolution in general), that results in:
    • Volo.Payment.Paypal namespace not found
    • AbpPaymentPayPalDomainSharedModule not found (because the using fails)

  Fix

  1. Open src/Project.Domain.Shared/ProjectDomainSharedModule.cs
  2. Replace:

  using Volo.Payment.Paypal;
  

  with:

  using Volo.Payment.PayPal;
  

  3. Rebuild the solution.

  That should unblock compilation immediately (as you observed).

  If you want to avoid editing by hand after re-running module add, check the file right after abp add-module Volo.Payment and correct the casing before building.

  (Verified doc page for the module install command is below.)

  • https://abp.io/docs/latest/modules/payment

  ---

  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)

  Save Cancel
• 

  0

  PDarioJer created 3 months ago

  I just checked the documentation and there seems to be a mismatch with the namespaces in general

  Markdown supported.

  Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

  Save Cancel
• 

  0

  maliming created 3 months ago

  Support Team Fullstack Developer

  Hi,

  You're right, this is a casing bug on our side. The module registry that abp add-module reads reports the PayPal Domain.Shared module with the wrong namespace casing — Volo.Payment.Paypal instead of Volo.Payment.PayPal. The CLI writes that value as-is, so it adds using Volo.Payment.Paypal; to your *.Domain.Shared project, which doesn't match the real namespace and the build fails with CS0234/CS0246. That same casing inconsistency is what you're seeing as the two namespace groups in the API reference.

  Your manual fix is exactly the right one — keep using:

  using Volo.Payment.PayPal;
  

  We'll correct the casing in the module's package metadata so it's consistent and add-module no longer needs the manual edit. Thanks for digging into it and sharing the screenshot.

  Thanks

  Markdown supported.

  Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

  Save Cancel