Activities of "rexhxiao"

We are currently planning an upgrade of our system to ABP 10 and noticed that starting from ABP 10, the framework replaces AutoMapper with Mapperly as the default object mapping solution.

We would like to clarify the following points regarding this change:

Is it technically supported to use AutoMapper and Mapperly simultaneously within the same ABP 10+ application?

If both mapping libraries can coexist, are there any recommended best practices, limitations, or potential conflicts we should be aware of?

From the framework design perspective, does ABP 10 intend for Mapperly to fully replace AutoMapper, meaning that projects upgrading to ABP 10 are expected to standardize entirely on Mapperly?

If partial coexistence is possible, would this be officially supported long-term, or is it only considered a temporary transition approach?

Are there any migration guidelines or recommended strategies for projects that have extensive existing AutoMapper profiles and mappings?

Our current system contains a significant number of existing AutoMapper configurations. Before making architectural decisions, we would like to understand whether we must fully migrate to Mapperly or whether a phased transition strategy is officially supported and recommended.

Thank you very much for your guidance. We appreciate your clarification so that we can make the appropriate architectural decision for our upgrade.

Let’s check it again ourselves to make sure.

Using ABP 8, here is the online URL: https://imm.koimpact.tw/

We are using Angular + AuthServer (OpenIddict) for authentication, but the client reported that it takes 3-5 seconds from opening the application to reaching the login page. Is this normal, or how can we speed up this process?

Ok

I originally wanted to extend my subscription for one year. The original price was discounted by 40%, but why is the Black Friday discount even smaller now?

You can see the issue by referencing both themes in the same project: typeof(AbpAspNetCoreMvcUiLeptonThemeModule) typeof(AbpAspNetCoreMvcUiLeptonXThemeModule)

The issue is the same for both frontend and backend - we have not overridden Account/Register. Here are the online URLs: https://www.snapglobal.shop (Snap tenant) https://mulan.reni.com.tw (Please switch to the Snap tenant)

For example, I set the password length to 3 in the backend, but the frontend validation still requires a length of 6 when submitting.

I tried to resolve it through inheritance, but it caused another error.

using Microsoft.Extensions.DependencyInjection;
using Volo.Abp.AspNetCore.Mvc.UI.Bundling;
using Volo.Abp.AspNetCore.Mvc.UI.Packages.JsTree;
using Volo.Abp.AspNetCore.Mvc.UI.Theme.Lepton;
using Volo.Abp.AspNetCore.Mvc.UI.Theme.Lepton.Bundling;
using Volo.Abp.AspNetCore.Mvc.UI.Theme.Lepton.ObjectMapping;
using Volo.Abp.AspNetCore.Mvc.UI.Theme.Lepton.Themes.Lepton.Libraries.JsTree;
using Volo.Abp.AspNetCore.Mvc.UI.Theme.Lepton.Toolbars;
using Volo.Abp.AspNetCore.Mvc.UI.Theme.Shared;
using Volo.Abp.AspNetCore.Mvc.UI.Theme.Shared.Bundling;
using Volo.Abp.AspNetCore.Mvc.UI.Theme.Shared.Toolbars;
using Volo.Abp.AspNetCore.Mvc.UI.Theming;
using Volo.Abp.AutoMapper;
using Volo.Abp.Modularity;
using Volo.Abp.VirtualFileSystem;

namespace Mulan.One.Public.Web.Themes.Lepton;

public class MulanAbpAspNetCoreMvcUiLeptonThemeModule : AbpAspNetCoreMvcUiLeptonThemeModule
{
    public override void ConfigureServices(ServiceConfigurationContext context)
    {
        Configure<AbpThemingOptions>(options =>
        {
            options.Themes.Add<LeptonTheme>();

            if (options.DefaultThemeName == null)
            {
                options.DefaultThemeName = LeptonTheme.Name;
            }
        });

        // 和 LeptonXTheme 重覆了，會造成 runtime 錯誤
        // ArgumentException: An item with the same key has already been added. Key: 401
        // Configure<AbpErrorPageOptions>(options =>
        // {
        //     options.ErrorViewUrls.Add("401", "~/Views/Error/401.cshtml");
        //     options.ErrorViewUrls.Add("403", "~/Views/Error/403.cshtml");
        //     options.ErrorViewUrls.Add("404", "~/Views/Error/404.cshtml");
        //     options.ErrorViewUrls.Add("500", "~/Views/Error/500.cshtml");
        // });

        Configure<AbpVirtualFileSystemOptions>(options =>
        {
            options.FileSets.AddEmbedded<AbpAspNetCoreMvcUiLeptonThemeModule>();
        });

        Configure<AbpToolbarOptions>(options =>
        {
            options.Contributors.Add(new LeptonThemeMainTopToolbarContributor());
        });

        Configure<AbpBundlingOptions>(options =>
        {
            options
                .StyleBundles
                .Add(LeptonThemeBundles.Styles.Global, bundle =>
                {
                    bundle
                        .AddBaseBundles(StandardBundles.Styles.Global)
                        .AddContributors(typeof(LeptonGlobalStyleContributor));
                });

            options
                .ScriptBundles
                .Add(LeptonThemeBundles.Scripts.Global, bundle =>
                {
                    bundle
                        .AddBaseBundles(StandardBundles.Scripts.Global)
                        .AddContributors(typeof(LeptonGlobalScriptContributor));
                });
        });

        Configure<AbpBundleContributorOptions>(options =>
        {
            options.Extensions<JsTreeStyleContributor>()
                .Add<LeptonJsTreeStyleContributorExtension>();
        });

        context.Services.AddAutoMapperObjectMapper<AbpAspNetCoreMvcUiLeptonThemeModule>();

        Configure<AbpAutoMapperOptions>(options =>
        {
            options.AddProfile<LeptonThemeAutoMapperProfile>(validate: true);
        });
    }
}

Are there any solutions to this problem?