When running the command abp add-module Volo.Payment to install the Payment module, the installation encounters the following errors:
\Project\src\Project.Domain.Shared\ProjectDomainSharedModule.cs(24,20): error CS0234: Der Typ- oder Namespacename "Paypal" ist im Namespace "Volo.Payment" nicht vorhanden. (Möglicherweise fehlt ein Assemblyverweis.)
\Project\src\Project.Domain.Shared\ProjectDomainSharedModule.cs(50,23): error CS0246: Der Typ- oder Namespacename "AbpPaymentPayPalDomainSharedModule" wurde nicht gefunden (möglicherweise fehlt eine using-Direktive oder ein Assemblyverweis).
The cause of this is a type in the ProjectDomainSharedModule. It includes it with "using Volo.Payment.Paypal;" instead of "using Volo.Payment.PayPal;"
Resolving the typo fixed the issue
As the title suggests, when you a modular Application with an initial module and install it, you get type errors. The integration model that the generator uses seems to be itself broken. I've fixed it temporarily by adding a manual symlink in the symlink-config.ps1 file but I don't know how stable that will be.
[yekalkan] said: Hi @PDarioJer
We've removed the ABP Studio MCP server support after the launch of ABP Agent.
We also removed the document but somehow it is still present. We'll check it.
https://github.com/abpframework/abp/pull/25518/
Thanks for the info, is there another way to use installed coding AI tools (codex, claude, etc.) to work with ABP instead of the AI Agent? A skill or a plug-in maybe?
[alper] said: can we test this MCP server on our side? can you provide information about this MCP
It is the MCP Server that is supposed to start with ABP Studio directly. The one defined here https://abp.io/docs/latest/studio/model-context-protocol
The logs unfortunately show neither that a connection has been succesfull or unsuccesful. Procmon and eventviewer also showed no error related to the mcp server. Whatever it is, it fails silently.
We are going to try installing ABP Studio on a fresh PC on a vanilla Windows installation and without any policies to make sure this is not an issue on our organization now.
The MCP Server for my ABP Studio 3.0.4 installation is not starting up. I've already tried reinstalling and deleting the .abp/studio folder, as well as reverting to 3.0.3 but the issue persists. I tried it on a colleague's PC and the issue was the same.
Steps to reproduce the issue:
Hello Support-Team,
we've recently renewed our license on a new organization (Jeremias). However, my user is still in the old one (Jeremias Group), which causes some conflicts. For example, I still get the reminder that I should renew my license. When using ABP Studio, I also default to Jeremias Group there.
Can you please remove me from the old Jeremias Group org?
Best regards Dario
Fair enough :) In any case, the original problem is solved. Thanks for the help!
Actually, I found this post while looking for a solution: https://github.com/bUnit-dev/bUnit/discussions/305 Removing the SetupModule from the Testbase and replacing it with
testContext.JSInterop.Mode = JSRuntimeMode.Loose;
did the trick. I can work with this for now. Though, if you have any concerns with this approach, I would be open to hear them. I gotta admit that I don't fully understand what is going on here.