Activities of "EngincanV"

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.

Hi, as far as I see in the code that you shared, the password icon part is commented out:

                          @*   <span class="input-group-text" id="togglePassword" style="cursor: pointer;">
                                <i class="fa fa-eye" id="eyeIcon"></i>
                            </span> *@

You've probably commented out because you are unable to see the related icon as you said. As you can see from the code above, we are using fa fa-eye classes for the icons, which correspond to the related icons in the Font Awesome library. So, you can either add the related library to your code, or change it as below to make it to use bootstrap icons:

                             <span class="input-group-text" id="togglePassword" style="cursor: pointer;">
-                               <i class="fa fa-eye" id="eyeIcon"></i>
+                               <i class="bi bi-eye-slash" id="eyeIcon"></i>
                            </span>

Change the icon class as bi bi-eye-slash to use Bootstrap icons.

Hi berkansasmaz,

I tried using the "Upgrade to Pro" option in ABP Studio, but I don’t see it available for any of the projects in our solution.

If I'm not mistaken, the screenshots you shared show a project using ABP 9+ being upgraded to Pro. However, our current project is still on version 8.0.5.

Regards, Gabriel

Hi, indeed we have added this feature with v0.6.8 (ABP Studio version), and it corresponds to ABP v8.1.3. So, it's normal to not see the related option.

So, you can update your ABP Studio CLI with the following command:

dotnet tool update -g Volo.Abp.Studio.Cli --version 0.6.8

and then upgrade your solution to pro with the following command:

abp upgrade -t app

Also, you can pass modules as arguments, see https://abp.io/docs/9.2/guides/migrating-from-open-source#migrating-from-open-source-templates

Hi, the code_verifier parameter is used to have an additional layer of security with PKCE.

In the production mode, you should generate ProductionEncryptionAndSigningCertificate and it seems you are already doing that, but can you please confirm the xxxx part (password of the certificate) is a real value, and it matches with the password value in your configuration:

public override void PreConfigureServices(ServiceConfigurationContext context)
{
    var hostingEnvironment = context.Services.GetHostingEnvironment();

    if (!hostingEnvironment.IsDevelopment())
    {
       PreConfigure<AbpOpenIddictAspNetCoreOptions>(options =>
       {
          options.AddDevelopmentEncryptionAndSigningCertificate = false;
       });

       PreConfigure<OpenIddictServerBuilder>(serverBuilder =>
       {
           //should match with this 👇
          serverBuilder.AddProductionEncryptionAndSigningCertificate("openiddict.pfx", "xxxx"); 
       });
    }
}

Also, you can refer to our Configuring OpenIddict documentation for further info.

Hi,

This page should dynamically reflect the custom property values. However, based on my understanding, ABP does not currently support automatically displaying these extra values on a separate page out of the box.

Yes, that's right. This requires some manual work.

I'll create an issue for your request, so we can evaluate it later. But, in the meantime, it can be beneficial for you to check the CreateModel and UpdateModal files of the Users/Index.cshtml page from our repository: https://github.com/abpframework/abp/blob/dev/modules/identity/src/Volo.Abp.Identity.Web/Pages/Identity/Users/CreateModal.cshtml#L42-L71

By checking the CreateModal.cshtml file, you can see how we are showing the generic part in our own create-update models, and follow a similar approach in your own case.

Regards.

yes, its there. it was working fine before upgrading to 9.1.1

Okay, interesting to hear that. I will create a new template with v9.1.1 and try to reproduce it, but in the meantime, by any chance, can you please share the error message in the failed unit test and the failed tests?