Activities of "niall"

I know the best way is reference modules in application project and migrations all database. This is in line with DDD's architectural design. But my platform needs loads modules as plugin, so i must migrate the database in module. i modify the module template, and resolved most issue, now it works fine.

I know shouldn't add DbContextFactory and migrations for the EntityFrameworkCoreModule, but there is no better option at the moment.I just want to know some technical details to redesign later.

Get down to business, Is AbpDbContextOptions a singleton for the entire life of the runtime?

Thanks , I understand it.

But I would like to know some details.

Base the EntityFrameworkCoreModule of module template, add DbContextFactory to configure the DBMS. but this class is only valid for EntityFrameworkCore tool?

Real database provided by App at runtime? So if MyApp use SQLServer, but MyModule migrated by MySQL, will throw exception?

Is there a way to let MyModule will decide which database provider will be used?

I notice the the EntityFrameworkCoreModule of MyApp can use options.UseMySQL(); to change the DBMS.

public class MyAppEntityFrameworkCoreModule : AbpModule
{
    public override void PreConfigureServices(ServiceConfigurationContext context)
    {
        BaaSoEfCoreEntityExtensionMappings.Configure();
    }

    public override void ConfigureServices(ServiceConfigurationContext context)
    {
        context.Services.AddAbpDbContext<BaaSoDbContext>(options =>
        {
            options.AddDefaultRepositories(includeAllEntities: true);
        });

        context.Services.AddAbpDbContext<BaaSoTenantDbContext>(options =>
        {
            options.AddDefaultRepositories(includeAllEntities: true);
        });

        Configure<AbpDbContextOptions>(options =>
        {
                /* The main point to change your DBMS.
                 * See also BaaSoDbContextFactoryBase for EF Core tooling. */
            options.UseMySQL();
        });

    }
}

Yes, the project created by SUITE is pro, now resolved it. Thanks!

OK, Thanks!

HAH, it works.

but a new issue, I only updated the basic to leptonx, but some ui need update to pro, such as account.

Is there a document to explain how to update them?

for example. i notice them at pro project.

    <PackageReference Include="Volo.Abp.Identity.Pro.Web" Version="8.2.2" />
    <PackageReference Include="Volo.Abp.Account.Pro.Admin.Web" Version="8.2.2" />
    <PackageReference Include="Volo.Abp.Account.Pro.Public.Web.Impersonation" Version="8.2.2" />
    <PackageReference Include="Volo.Abp.Account.Pro.Public.Web.Shared" Version="8.2.2" />
    <PackageReference Include="Volo.Abp.OpenIddict.Pro.Web" Version="8.2.2" />

but at basic like this:

    <PackageReference Include="Volo.Abp.Account.Web.OpenIddict" Version="8.2.2" />

How do the module of the Basic and Professional correspond?

I just want to get a pro module template. Or can you generate one for me?

OK, I understand.

I have seen this example, but considering that implementing a DDD architecture on my own is too complicated, that's why I want to use templates project directly.

What are the potential risks if using a template as a plugin?

Hi，

I update the basic to leptonX manually. but got a error tip me need license.

ABP-LIC-0020 - License code not found! Ensure that your appsettings.json or appsettings.secrets.json has "AbpLicenseCode" key with your license code.

How do i generate the license manually in my project?

Oh, So you mean My.Plugin simply inherits AbpModule without using a module template?

If depend a new module, Is need rebuild the My.Platform?

I notice the document and example at https://abp.io/docs/latest/framework/architecture/modularity/plugin-modules , the plugin is a AbpModule too. How do I understand your answer? -- "The My.Plugin is a module. It would be best not to use it as a Plugin."