Please lets set up a call on Monday
Hi, as you mentioned, a quick call would be helpful to check and resolve these issues efficiently—it'll benefit both sides.
Could you please schedule a meeting via https://abp.io/demo? When booking, kindly include the ticket number and a brief description of the problem so we can prepare accordingly and assist you better during the session.
Looking forward to speaking with you. Best regards,
Hi, can you please give me more details?
For example, sharing the app service definitions, the ts file where you send the request to the relevant service, and any additional steps. These information can be extremely helpful for us to better assist you.
Hi, there is a class named IdentityGdprEventHandler in the Identity Pro Module (domain layer) and it's responsible for subscribing to the GdprUserDataDeletionRequestedEto, anonymizing the user and then deleting the user.
Since you're using a microservices architecture, there can be multiple handlers attempting to retrieve and process the same user. To improve this, we’ll enhance the IdentityGdprEventHandler so that it gracefully does nothing if the user cannot be found, instead of causing an error.
I'll check this and fix the problem. Your ticket is refunded. Thanks for reporting.
Best Regards.
Hi, please apply the following steps then your problem should be fixed:
1.-) Close the ABP Studio application 2.-) Clear the local dotnet cache with the following command:
dotnet nuget locals all --clear
3.-) Open the ABP Studio application or run ABP Studio CLI.
Please let me know if it fixes your problem or not. Regards.
Note: This problem seems it occurred because there was a problem in your local dotnet cache. ABP Studio templates come from the related dll and after the first installation of the extension, we use it through the local cache of your PC.
Strange. It only generates json file for me. I am stuck and there is not error to look into.
Mine project is blazor server based and you are using blazor web app template. It is possible for you to try it with blazor server template?
FYI proxies are created for abp
but not myPrabh
Hi, I've checked with your exact configuration, but still could not reproduce it, please see the steps below:
1-) Created microservice solution:
2-) Created a new service called MyPrabhService (and also created a dummy appservice -> ProductAppService.cs)
3-) Then, run all services and try to generate client proxies:
All of the proxies are generated correctly ( I only defined GetProductsAsync method in my dummy ProductAppService class):
Please ensure that you have created the server by using our Microservice template, and in your blazor-server project there is a configuration as below:
context.Services.AddStaticHttpClientProxies(typeof(Issue9128BzServerMyPrabhServiceContractsModule).Assembly);
Hello ok, I will try it on a different environment. But what can be different on different environment it does not make sense. So weird i will let you know when i try it.
Thanks, waiting for your response.
Hi, you should run your service while generating client proxies. To demonstrate it, I have created a CatalogMicroservice and then, expanded my blazor webapp project, right-click to generate client-proxies and you can see the configuration below:
Then, when it's completed:
I can see the client-proxies in my project:
Hi, in ABP Studio templates we rely on the related extension and therefore after the first install of the related extension, we are using dotnet local cache and get the templates from the related extension.
So, if you clear your local cache it should fix the problem, and in the next time, when you open ABP Studio or run any ABP Studio CLI command, then it should install the related extension package.
So, please clear your local cache with the following command:
dotnet nuget locals all --clear
and then run ABP Studio or execute a CLI command.
Regards.
Thanks EngincanV that is quite helpful. I will use this method from now on.
But I would like to inform you that I am still not able to see proxies yet.
Thanks for your prompt response. Let me check it and write you back then.
Hi, here are the answers to some of your questions:
Should we override the ProfileAppService or the ProfileController?
To apply business logic like password history checks, overriding the ProfileAppService is the right and recommended approach.
The ProfileController in Volo.Abp.Account.Pro is just a thin wrapper that calls into the IProfileAppService. So you don’t need to replace the controller if your goal is only to apply logic like password history checks.
Could there be issues with the lifetime or DI registration that conflict between our custom implementation and the built‑in services, and if so, what is the best way to resolve them?
To answer this question properly, can you set a breakpoint to your own implementation and let me know if they are called or not?
After the confirmation, I can assist you better.
Regards.
