Activities of "rcalv002"

hello support, would you take a look at a project? Do you have a guide that shows the settings between prod and dev operational for us new devs?

Hi gterdem,

I had already tried the strictdiscoverydocumentvalidation one but not the skipissuercheck. When I use skipissuercheck it does not throw the error but it just doesnt go to the identity server login page. anything else i need to check ?

The issue turned out to be use of async via AsyncHelper.RunSync in a singleton constructor: my bad.

Thanks!

Hi Liang,

Yes the recurring worker jobs are okay, in my sample i triggered queued for processing various non-recurring worker jobs that take TransactionProcessingArgs. You can see in the screenshots above, maybe trigger a bunch of these. You should get failures since you dont have keys to use the domain service and these will end up in retry states. Stop the application and try again? Any time I have jobs in the hangfire.jobs table it wouldnt start back up

Shared via mail, thanks

maliming, I also see other problems with the template. I've compared against standard app template.

In standard app template:

• Generate fresh template with abp new prodrelease -t app
• run dbmigrator
• Set ASPNETCORE_ENVIRONMENT to Production
• Add an entry to en.json localization
• Login to frontend, localization content is fine.
• Validate by calling /api/abp/application-configuration you can see the new entry under prodrelease node of localization

In nolayer

• Generate fresh template with abp new prodrelease -t app
• run dbmigrator
• Set ASPNETCORE_ENVIRONMENT to Production
• Add an entry to en.json localization
• Login to frontend, localization content from json in local project is not fine, you see the Welcome_Title instead of the localized text
• Validate by calling /api/abp/application-configuration you can not see the new nor any project specific entry under prodrelease node of localization . This issue also seems to affect other embedded content, like for example if you create a new settings component to have custom settings, this content doesnt get loaded in Production build unless you copy the Components folder to the bin folder where the production build is generated.

Thanks. In the snippet below, the template also seems to be missing the automapper module registration

private void ConfigureAutoMapper(IServiceCollection services)
    {
        services.AddAutoMapperObjectMapper<MyModule>(); // This line seems to be missing too
        Configure<AbpAutoMapperOptions>(options =>
        {
            /* Uncomment `validate: true` if you want to enable the Configuration Validation feature.
             * See AutoMapper's documentation to learn what it is:
             * https://docs.automapper.org/en/stable/Configuration-validation.html
             */
            options.AddMaps<MyModule>(/* validate: true */);
        });
    }

Can you confirm?

Yes this worked, should this be part of the standard template ?

Perfect that worked, I'm not sure why that line was added ( I definitely did not add it manually to the project)

Thanks again!

sent via email