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.
Hi, If you are using ABP Studio, then in your final application, you can directly generate C# proxies, through ABP Studio UI. Please check https://abp.io/docs/latest/tutorials/microservice/part-03#generating-the-ui-proxy (this is explained for MVC, but it's not so different in the Blazor side, you should do it in your final blazor application)
I guess what I'm more asking is, can we utilize the generation process that the Suite tool uses to dynamically add code or is this not catered for and one must manually add code via extensions for additional standard endpoints.
Actually, ABP Suite's templating system are just for defining some common and static configurations. In the code side, we are extending it with the required services.
So, it's always a better option to go with the second option: "is this not catered for and one must manually add code via extensions for additional standard endpoints"
Can you please confirm one more thing, using hangfire will execute multiple jobs at the same time as multithreading?
Yes, Hangfire can execute multiple jobs concurrently using background threads. It utilizes multithreading based on the number of worker threads configured in the Hangfire Server. By default, Hangfire can process several jobs in parallel depending on your server's capacity and configuration.
It is working when I'm using [Queue("default")], is it fine to use default queue ?
Yes, it's perfectly fine to use the "default" queue in Hangfire. In fact, if you don't specify a queue explicitly, Hangfire will automatically use the "default" queue for all background jobs.
But it should normally work with other queues, I'll investigate this.
Hi, in v9.1.1 we upgraded the Hangfire.AspNetCore from v1.8.17 to v1.8.18 and it seems this is the reason for the problem (https://github.com/HangfireIO/Hangfire/issues/2437). So, in your application, you can manually set its version to v1.8.17 for a quick workaround, and then it should start working again as expected:
<PackageReference Include="Hangfire.SqlServer" Version="1.8.17" />
<PackageReference Include="Hangfire.AspNetCore" Version="1.8.17" />
Hi, thanks for the detailed information.
You are right that ABP Suite, searches for all files containing the term "{EntityName}DeletedEventHandler" and then re-generates it for the master entity. To overcome this problem, as you stated, it can be good to create a new deleted event handler with a different name.
Thanks for clearing out the possible problem, I'll create an internal issue for that and we will evaluate it and also notice that I've refunded your ticket.
Best Regards.
