Move Quartz property binding into AbpQuartzSqlInstallerModule so the migrator and service use the same installer configuration. Align provider connection names, set the QRTZ_ table prefix, and quote the SQL Server database name when creating it.
Keep the base configuration provider-neutral, enable Elsa UserTasks only in provider-specific files, format the base settings, and align Quartz connection string names.
Register the approval flow, user tasks and identity services in AllInOne, expose the API route through the gateway, add the navigation entries and apply the merged approval database migrations.
Rename the single (monolith) application, its migration projects and the
associated solution file to follow the LINGYUN.Abp.MicroService.* naming
convention.
Renamed projects:
- LY.MicroService.Applications.Single
-> LINGYUN.Abp.MicroService.AllInOne
- LY.MicroService.Applications.Single.EntityFrameworkCore
-> LINGYUN.Abp.MicroService.AllInOne.EntityFrameworkCore
- LY.MicroService.Applications.Single.EntityFrameworkCore.MySql
-> LINGYUN.Abp.MicroService.AllInOne.EntityFrameworkCore.MySql
- LY.MicroService.Applications.Single.EntityFrameworkCore.PostgreSql
-> LINGYUN.Abp.MicroService.AllInOne.EntityFrameworkCore.PostgreSql
- LY.MicroService.Applications.Single.EntityFrameworkCore.SqlServer
-> LINGYUN.Abp.MicroService.AllInOne.EntityFrameworkCore.SqlServer
- LY.MicroService.Applications.Single.DbMigrator
-> LINGYUN.Abp.MicroService.AllInOne.DbMigrator
- aspnet-core/LINGYUN.MicroService.SingleProject.slnx
-> aspnet-core/LINGYUN.MicroService.AllInOne.slnx
Renamed identifiers:
- MicroServiceApplicationsSingleModule -> AllInOneModule
(AllInOneModule.cs, AllInOneModule.Configure.cs, referenced from Program.cs)
Also updated:
- namespaces, <RootNamespace>, ProjectReference paths and the solution entries
- Dockerfile entry point (LINGYUN.Abp.MicroService.AllInOne.dll)
- build/build-aspnetcore-common.ps1 (solution array)
- README.md / README.en.md (solution list) and the project READMEs / docs that
referenced the previous names
Code fixes required by the new namespace (namespaces under LINGYUN.Abp shadow
top-level namespaces):
- SingleMigrationsDbContext: fully qualify LINGYUN.Platform.Datas.Data, because
the simple name Data now resolves to the LINGYUN.Abp.Data.* namespace
- AllInOneModule.Configure: use global::Elsa.* for the Elsa startup types,
because Elsa.Activities.* now resolves to LINGYUN.Abp.Elsa.Activities.*
(Elsa.Activities.Webhooks.Startup would otherwise silently bind to the wrong type)
BREAKING CHANGE: assembly names, namespaces, the Docker entry point and the
published package ids of the migration projects changed. Consumers must update
their references:
- LY.MicroService.Applications.Single.EntityFrameworkCore
-> LINGYUN.Abp.MicroService.AllInOne.EntityFrameworkCore
- LY.MicroService.Applications.Single.EntityFrameworkCore.MySql
-> LINGYUN.Abp.MicroService.AllInOne.EntityFrameworkCore.MySql
- LY.MicroService.Applications.Single.EntityFrameworkCore.PostgreSql
-> LINGYUN.Abp.MicroService.AllInOne.EntityFrameworkCore.PostgreSql
- LY.MicroService.Applications.Single.EntityFrameworkCore.SqlServer
-> LINGYUN.Abp.MicroService.AllInOne.EntityFrameworkCore.SqlServer
- LY.MicroService.Applications.Single.DbMigrator
-> LINGYUN.Abp.MicroService.AllInOne.DbMigrator
Stale package artifacts in the LocalNuget output folders were removed; rebuild
(or pack) to regenerate them with the new names.
Verified:
- dotnet build aspnet-core/LINGYUN.MicroService.AllInOne.slnx (0 errors)
- all six renamed projects build with 0 errors
- 196 tracked files were relocated (193 detected as renames), no tracked file lost
- text scan for the previous names returns no remaining references
Note: aspnet-core/templates/aio still declares MicroServiceApplicationsSingleModule;
renaming the AIO template is intentionally left for a follow-up.