Activities of "DominaTang"

Our angular project has account module source code from ABP 7.2.3. The personal-setting.component.ts, when click save button, it calls the line this.configState.refreshAppState(); and throw 500 error. From network table it trying to reach the Administration Micro Service's ps://localhost:44325/api/abp/application-configuration?includeLocalizationResources=false 500 (Internal Server Error) But if directly call Administration Micros service's swagger API, there is no any issue. From the Gateway Log: [INF] Proxying to https://localhost:44367/api/abp/application-configuration?includeLocalizationResources=false HTTP/2 RequestVersionOrLower [INF] Received HTTP/2.0 response 500.

From Administration Micro Service log: 2025-04-29 15:34:28.792 -04:00 [INF] CORS policy execution failed. 2025-04-29 15:34:28.792 -04:00 [INF] Request origin http://localhost:4200 does not have permission to access the resource. 2025-04-29 15:34:28.797 -04:00 [ERR] An error occurred using the connection to database '' on server ''. 2025-04-29 15:34:28.797 -04:00 [ERR] An exception occurred while iterating over the results of a query for context type 'Bdo.Ess.IdentityService.EntityFrameworkCore.IdentityServiceDbContext'. System.InvalidOperationException: The ConnectionString property has not been initialized.

It looks like that Administration Service try to access identity Service and database connection string is empty? The weird thing is, after click go to the home and click save button on use setting page, there is no exception thrown.

MicroService Template

After upgrading from 8.1.x to 9.1.1. When click the user profile icon on top right corner, we has custom code (replace component that only keep my account and logout) menu items.

But the main issue is, when click any of menu item, the browser address URL is actually Auth server's URL. so that the left side menu is empty (not the angular app's left side menu, when click logo icon in left side top, it navigate to Auth server's home page instead of Angular app's home page.

Also we have downloaded source code of Angular account module (Abp 7.2.3) and modify some code. We want to keep using Angular's /account/management, instead of Auth server's manage account. How to do that?

Micro Service Template

In APP_ROUTE_PROVIDER, there is code routes.remove([eThemeSharedRouteNames.Administration]); And then there is code

{
        path: '/identity/roles',
        name: '::Roles',
        parentName: '::Administration',
        layout: eLayoutType.application,
        requiredPolicy: Permissions.ABPIDENTITY_ROLES,
      } as ABP.Route,
      {
        path: '/identity/users',
        name: '::Users',
        parentName: '::Administration',
        layout: eLayoutType.application,
        requiredPolicy: Permissions.ABPIDENTITY_USERS,
      } as ABP.Route,

Which means the app would only keeps two menu items under administration menu, however, after upgrade there are two administration side menu;

And when click Roles or Users menu, there is error: core.mjs:6843 ERROR RuntimeError: NG04014: Invalid configuration of route 'identity/'. The component must be standalone. In source code there is identity routes which replace Roles component:

export const Identity_ROUTES: Routes = [
  { path: '', redirectTo: 'roles', pathMatch: 'full' },
  {
    path: '',
    component: RouterOutletComponent,
    canActivate: [authGuard, permissionGuard, IdentityExtensionsGuard],
    children: [
      {
        path: 'roles',
        component: ReplaceableRouteContainerComponent,
        data: {
          requiredPolicy: 'AbpIdentity.Roles',
          replaceableComponent: {
            key: eIdentityComponents.Roles,
            defaultComponent: RolesComponent,
          } as ReplaceableComponents.RouteData<RolesComponent>,
        },
      },

....

Hi,

I got this build error warning "@volo/abp.ng.account > angularx-qrcode@17.0.1" has incorrect peer dependency "@angular/core@^17.0.0". warning "@volosoft/abp.ng.theme.lepton-x > @ng-bootstrap/ng-bootstrap@17.0.1" has incorrect peer dependency "@angular/common@^18.0.0". warning "@volosoft/abp.ng.theme.lepton-x > @ng-bootstrap/ng-bootstrap@17.0.1" has incorrect peer dependency "@angular/core@^18.0.0". warning "@volosoft/abp.ng.theme.lepton-x > @ng-bootstrap/ng-bootstrap@17.0.1" has incorrect peer dependency "@angular/forms@^18.0.0". warning "@volosoft/abp.ng.theme.lepton-x > @ng-bootstrap/ng-bootstrap@17.0.1" has incorrect peer dependency "@angular/localize@^18.0.0". warning "@volosoft/abp.ng.theme.lepton-x > @ng-bootstrap/ng-bootstrap@17.0.1" has unmet peer dependency "@popperjs/core@^2.11.8".

In my package.json: @volosoft/abp.ng.theme.lepton-x": "4.1.1", "@angular/core": "~19.1.0" ...

Can I above warnings?

Thanks,

If it possible make Angular project to be stand-alone: true after upgrade to Angular 19.

if yes, what these two components come from which ABP module: <abp-loader-bar></abp-loader-bar> <abp-dynamic-layout></abp-dynamic-layout>

Micro Services application.

For the ABP 9 project templated created by ABP studio. There are new micro services created, audit-logging and language. When I upgrade existing ABP 8 solution, do I have to add these two new micro services to solution?

In administration micro service, there are three new connection strings added, do I have to add them when upgrading? "AuditLoggingService": "Server=localhost,1434; User Id=sa; Password=myPassw@rd; Database=Ess_AuditLoggingService; TrustServerCertificate=true; Connect Timeout=240;", "LanguageService": "Server=localhost,1434; User Id=sa; Password=myPassw@rd; Database=Ess_LanguageService; TrustServerCertificate=true; Connect Timeout=240;", "AbpBlobStoring": "Server=localhost,1434; User Id=sa; Password=myPassw@rd; Database=Ess_BlobStoring; TrustServerCertificate=true; Connect Timeout=240;"

In Administration Db context, ABP 9 code:

[ConnectionStringName(DatabaseName)] [ReplaceDbContext( typeof(IPermissionManagementDbContext), typeof(IFeatureManagementDbContext), typeof(ITextTemplateManagementDbContext), typeof(ISettingManagementDbContext) )] public class AdministrationServiceDbContext : AbpDbContext<AdministrationServiceDbContext>, IPermissionManagementDbContext, IFeatureManagementDbContext, ISettingManagementDbContext, ITextTemplateManagementDbContext, IHasEventInbox, IHasEventOutbox

ABP 8 code: [ConnectionStringName(AdministrationServiceDbProperties.ConnectionStringName)] public class AdministrationServiceDbContext : AbpDbContext<AdministrationServiceDbContext>, IPermissionManagementDbContext, ISettingManagementDbContext, IFeatureManagementDbContext, IAuditLoggingDbContext, ILanguageManagementDbContext, ITextTemplateManagementDbContext, IBlobStoringDbContext

Do I have to modify DbConext accordingly?

I am upgrading from ABP 8.2.3 to ABP 9, from the project template I created with ABP Studio, I noticed that OpenId seeding is within Identity Micro Service instead of standalone DBMigrator project. However, I notice that CreateOrUpdateApplicationAsync() method is only called for Swagger UI, Angular, Public Web and Web. There is not call for each Micro Services. How each Micro Service talk with Auth Server then?

ABP framework 8.2.3 (going to upgrade to 9), Micro Services

In one of app micro service, we are going to change from Mongo Db to Azure Cosmos DB to use COSMOS Db's encryption feature. https://devblogs.microsoft.com/cosmosdb/always-encrypted/ https://github.com/Azure/azure-cosmos-dotnet-v3/blob/master/Microsoft.Azure.Cosmos.Samples/Usage/Encryption/Program.cs

Do you think it is possible. I don't see any place I can inject Cosmos DB's encryption package.

Thank

Abp Framework 8.2.3, Micro Services. I tried the following test code:

public abstract class SampleAppService_Tests<TStartupModule> : AdministrationServiceApplicationTestBase<TStartupModule>
    where TStartupModule : IAbpModule
{
    private readonly IPermissionAppService _permissionAppService;
    protected SampleAppService_Tests()
    {
        _permissionAppService = GetRequiredService<IPermissionAppService>();
    }

    [Fact]
    public async Task Should_Get_Permissions()
    {
        var permissions = await _permissionAppService.GetAsync(RolePermissionValueProvider.ProviderName, "admin");

        permissions.ShouldNotBeNull();
        permissions.EntityDisplayName.ShouldBe("admin");
        permissions.Groups.Count.ShouldBeGreaterThanOrEqualTo(1);
        permissions.Groups.SelectMany(x => x.Permissions).Count().ShouldBeGreaterThanOrEqualTo(1);
    }
}

The code throw exception: Autofac.Core.DependencyResolutionException : An exception was thrown while activating Volo.Abp.PermissionManagement.Identity.RolePermissionManagementProvider. ---- Autofac.Core.DependencyResolutionException : None of the constructors found on type 'Volo.Abp.PermissionManagement.Identity.RolePermissionManagementProvider' can be invoked with the available services and parameters: Cannot resolve parameter 'Volo.Abp.Identity.IUserRoleFinder userRoleFinder' of constructor 'Void .ctor(Volo.Abp.PermissionManagement.IPermissionGrantRepository, Volo.Abp.Guids.IGuidGenerator, Volo.Abp.MultiTenancy.ICurrentTenant, Volo.Abp.Identity.IUserRoleFinder)'.

The Azure Pipeline was good last Friday. But today it has this error: Unable to load the service index for source https://nuget.abp.io/9acf3724-93dd-4ab1-9a60-3123698a56a3/v3/index.json