Branch:
dev
2.9
3.0
3.1
3.2
3.3
4.0
4.1
4.2
4.3
4.4
4.4.1
4.4.2
4.4.3
5.0.0
5.0.0-rc.1
5.0.0-rc.2
5.1.1
5.1.3
5.1.4
5.2.0
5.2.1
5.2.2
6.0
6.0.0
6.0.0.1
aspire-integration
dependabot/npm_and_yarn/apps/vue/tests/server/follow-redirects-1.16.0
dependabot/npm_and_yarn/apps/vue/tests/server/lodash-4.18.1
dependabot/npm_and_yarn/apps/vue/tests/server/picomatch-2.3.2
dependabot/npm_and_yarn/apps/vue/tests/server/systeminformation-5.31.6
dependabot/npm_and_yarn/apps/vue/tests/server/vm2-3.11.5
dev
elsa-3.0
flutter
main
master
rel-10.0.2
rel-10.2.0
rel-10.4.0
rel-10.6.0
rel-10.7.0
rel-7.0.2
rel-7.0.3
rel-7.1.0
rel-7.1.1
rel-7.2.1
rel-7.3.2
rel-7.3.3
rel-7.4.0
rel-8.0.0
rel-8.0.3
rel-8.1.0
rel-8.1.1
rel-8.1.2
rel-8.1.3
rel-8.2.0
rel-8.2.1
rel-8.2.2
rel-8.3.0
rel-8.3.4
rel-9.1.1
rel-9.1.3
rel-9.2.0
rel-9.2.3
rel-9.3.1
rel-9.3.5
rel-9.3.6
upt-5.3.2
upt-5.3.4
upt-5.3.5
upt-6.0.1
upt-6.0.2
upt-7.0.0
upt-7.0.1
upt-7.2.1
upt-7.2.2
upt-7.4.0
upt-8.2.0
vben-5-7-0
10.0.2
10.2.0
10.4.0
10.6.0
10.7.0
3.2.1
3.2.2
3.2.3
3.3.0
3.3.1
3.3.2
4.0.0
4.4.0
4.4.3
5.0.0
5.0.0-rc.2
5.1.1
5.1.3
5.1.4
5.2.0
5.2.1
5.2.2
5.3.0
5.3.2
5.3.4
6.0.0
6.0.1
6.0.2
7.0.0
7.0.1
7.0.2
7.0.3
7.1.0
7.1.1
7.2.1
7.3.2
7.3.3
7.4.0
8.0.0
8.0.3
8.1.0
8.1.1
8.1.2
8.1.3
8.2.0
8.2.1
8.2.2
8.3.0
8.3.4
9.0.4
9.1.1
9.1.3
9.2.0
9.2.1
9.2.3
9.3.5
9.3.6
${ noResults }
5 Commits (dev)
| Author | SHA1 | Message | Date |
|---|---|---|---|
|
|
d1ccd2b2d4 |
feat(print-designer): add EF Core persistence and migrations
|
6 days ago |
|
|
1c2626ced5 |
feat(approval-flow): add database migrations and user task schema
Add the ElsaNext approval flow migrations for PostgreSQL, MySQL and SQL Server and configure PostgreSQL user-task schema mapping. |
4 weeks ago |
|
|
a4fe3f328e |
feat(approval-flow): integrate approval flow into AllInOne and gateway
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. |
4 weeks ago |
|
|
7ecf48b96f |
chore(build): Remove the redundant per-project Fody configuration
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 |
1 month ago |
|
|
ef4f52f181 |
refactor(allinone): Rename the single application to LINGYUN.Abp.MicroService.AllInOne
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.
|
1 month ago |