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.
Enable the provider-neutral EfCore feature flags for Elsa workflow management, runtime, alterations, agents, labels, secrets, weaver, and user tasks so AllInOne does not fall back to in-memory stores.
Move the Blazor pre-configuration into the partial module, consolidate Studio global usings, and avoid the CookieOptions ambiguity introduced by the broad components namespace import.
Serve the Elsa Studio Material icon fallback stylesheet from the AllInOne wwwroot so activity palette and workflow node icons render when external fonts are unavailable.
Replace the MVC identity and settings pages with the official ABP MudBlazor modules, add the Blazor Server host and Elsa Studio shell, route Studio and its in-process API through the host cookie, and register the SignalR connection configurator used by Studio UserTasks.
Reference every Elsa Studio Blazor extension, register their ABP modules in DependsOn, add the UserTasks Studio module, and include the new module in the AllInOne solution.
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.
The platform service renders the admin menu through AbpUINavigationVueVbenAdmin5Module, so the
v1 navigation, settings and theme modules are no longer part of it. Drop them from the solution
and from the service so the retired modules stop being built with everything else.
- remove LINGYUN.Abp.UI.Navigation.VueVbenAdmin, LINGYUN.Platform.Settings.VueVbenAdmin and
LINGYUN.Platform.Theme.VueVbenAdmin from LINGYUN.MicroService.All.slnx
- drop the Platform.Theme.VueVbenAdmin project reference and PlatformThemeVueVbenAdminModule from
the platform service, and restore the alphabetical order of the AspNetCore.Authentication using
The projects themselves are kept: the AIO template still references them as packages, and they
are still registered in the AllInOne and Aspire solutions.
The template card payload is written into the notification property bag as JSON and read
back when the notification is published, but TemplateCard is abstract, so Newtonsoft.Json
could never restore it ("Could not create an instance of type ... abstract class") and the
card was lost as soon as the notification was persisted or queued for a retry.
- add TemplateCardJsonConverter and TemplateCardSystemTextJsonConverter, which resolve the
concrete card from the card_type discriminator (read from the constructor IL, falling back
to the type name) and reject an unknown discriminator
- split NotificationDataWeChatWorkExtensions into partials per message type (file, mini
program, mp news, template card, text card, video, voice) and add the shared
TryGetMessagePayload helper that deserializes with the converter
- add the Safe, EnableIdTrans, EnableDuplicateCheck and DuplicateCheckInterval switches
- migrate TuiJuheNotificationPublishProvider to the NotificationPublishContext contract the
other providers already use, and skip the interceptors for notifications at or above Warn
- bind the WeChat Work mini program account through the new work-weixin/miniprogram/bind
endpoint using the code2session user id
- rename AbpNotificationOptions to AbpNotificationsPublishOptions in the tests, fix the SMS
test project reference, retarget the templating tests to net10.0, register the webhook
notification projects and add the missing IP2Region reference
configureawait.props now provides the ConfigureAwait weaver through the Fody 6.9.3
WeaverConfiguration property and sets FodyGenerateXsd=false, so the per-project
FodyWeavers.xml files and every FodyWeavers.xsd are redundant.
- delete 450 FodyWeavers.xml and 438 FodyWeavers.xsd from the framework, modules,
services, gateways, tests and migrations projects and from the micro service template
- every removed FodyWeavers.xml was equivalent to the default supplied by configureawait.props
(439 x <ConfigureAwait ContinueOnCapturedContext="false" />, 20 x <ConfigureAwait />, whose
default is ContinueOnCapturedContext=false, and 2 of those with an XML declaration); no
Blazor / AspNetCore.Components project carried one and the template manifests do not list them
- the aio template keeps its 22 files: its own Directory.Packages.props pins Fody 6.8.0, which
does not support the WeaverConfiguration property
- delete aspnet-core/services/LY.MicroService.IdentityServer[.HttpApi.Host],
aspnet-core/services/LY.AIO.Applications.Single and their
EntityFrameworkCore / DbMigrator projects
- drop the stale references in build/modules.dependencies.json and tye.yaml
- add AbpAuditLoggingIPLocationModule / AbpMaxMindGeoIP2Module to the startup modules of
every service, gateway and the Aspire hosts (project references included)
- enable AuditLogging:IPLocation:IsEnabled and IPLocation:RemoveCountry (中国) in
docker-compose and the hosts' appsettings.Development.json
Logging:
- reference LINGYUN.Abp.Logging.Serilog.OpenObserve and register
AbpLoggingSerilogOpenObserveModule (the Elasticsearch module is now declared
explicitly in the module dependencies)
- wrap the Serilog WriteTo pipeline in an Async sink and add an OpenTelemetry
sink (endpoint, protocol, resource attributes)
- set Logging:Provider to ElasticsearchLoggingProvider and add the OpenObserve
endpoint/token to the development settings
- add the Serilog.Sinks.Async / Serilog.Sinks.Console / Serilog.Sinks.OpenTelemetry
package references
- rotate the file sinks by size as well (rollOnFileSizeLimit, retainedFileCountLimit
50, fileSizeLimitBytes 5 MB)
Solutions:
- add LINGYUN.Abp.Logging.Serilog.OpenObserve to the AllInOne solution and remove
the duplicated /tests/ folder (those test projects stay in LINGYUN.MicroService.All.slnx)
- add LINGYUN.Abp.MaxMindGeoIP2 to the Aspire solution
Auth:
- accept the API resource audience of this host: AuthServer:ValidAudiences now also
contains "all_in_one" (the access token audience comes from the API scope resource
created in OpenIddictDataSeederContributor), so OpenIddict validation no longer
rejects tokens with ID2094
- the JwtBearer scheme now applies ValidAudiences from configuration as well, together
with the wildcard issuer validator configuration
Also: global usings tidied up (LINGYUN.Abp.IP.Location is no longer needed by the host).
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.