Activities of "DominaTang"

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

After upgrade to Abp 8 (BE use Abp 8.2.3) FE use 8.1.3 (For Saas menu display on ABP 8.2.3) Micro Service Architect

Click account , personal setting, the form content for this line not showing o UI <abp-extensible-form [selectedRecord]="storedProfile"></abp-extensible-form>

In ABP 7:

export interface ProfileDto extends ExtensibleObject {
    userName?: string;
    email?: string;
    emailConfirmed: boolean;
    name?: string;
    surname?: string;
    phoneNumber?: string;
    phoneNumberConfirmed: boolean;
    isExternal: boolean;
    hasPassword: boolean;
    concurrencyStamp?: string;
}

In ABP 8:

export interface ProfileDto extends ExtensibleObject {
    userName?: string;
    email?: string;
    emailConfirmed: boolean;
    name?: string;
    surname?: string;
    phoneNumber?: string;
    phoneNumberConfirmed: boolean;
    isExternal: boolean;
    hasPassword: boolean;
    supportsMultipleTimezone: boolean;
    timezone?: string;
    concurrencyStamp?: string;
}

But I think the Dto extra properties should not cause the issue. I create a ProfileDtoLocal as version 7 Dto and bind it to abp-extensible-form, but the UI still black.

Plus, I have a question though, the Dto has many properties, but even on ABP 7 UI only show:= 5 input contorls: User name,, Name, Surname, Email and Phone Number

What is the logic within abp-extensible-form to decide the input control rendered on UI?

ABP 8.2.3 MicroServices Template

When run application locally, after upgrade, the login page layout is good (same as before). However, after the application deployed, the layout is different. How to disable ABP script and css bundle, so that I can compare local version scripts/css and deployed version. I commented the line Config Bundle, the bundle is still there.

Also, I copy over every css, lib, theme folders/files and Theme package back to prior upgrade, the UI still not same as before. Don't understand why.

Thanks, Domina