Activities of "DominaTang"

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?

Switching to Cosmos DB (Mongo version) is very simply, just change connection string. the code seems working. Encryption seems not that easy.

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)'.

It is good now.

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

Our UI used to have User name, Name, Surname, Email and Phone Number -- these 5 input controls, Now it's have 0 input controls on UI. The whole form is blank and not rendered. It's not related to any extra properties.

Hi,

I can't reproduce the problem.

ObjectExtensionManager.Instance.Modules() 
  .ConfigureIdentity(identity => 
  { 
      identity.ConfigureUser(user => 
      { 
          user.AddOrUpdateProperty<string>( //property type: string 
              "SocialSecurityNumber", //property name 
              property => 
              { 
                  property.Attributes.Add(new RequiredAttribute()); 
                  property.Attributes.Add(new StringLengthAttribute(64) {MinimumLength = 4}); 
 
              } 
          ); 
 
          user.AddOrUpdateProperty<string>("Test"); 
          user.AddOrUpdateProperty<string>("Test2"); 
          user.AddOrUpdateProperty<string>("Test3"); 
          user.AddOrUpdateProperty<string>("Test4"); 
          user.AddOrUpdateProperty<string>("Test5"); 
          user.AddOrUpdateProperty<string>("Test6"); 
      }); 
  }); 

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

Here is the source code

https://github.com/abpframework/abp/blob/rel-8.0/npm/ng-packs/packages/components/extensible/src/lib/components/extensible-form/extensible-form.component.ts

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?

hi

What steps and code have you applied to the layout/theme?

Can you share the csproj file content for your web project?

I figured out the reason. Our local templates folder files are not pickup when deployed. Since in release mode, the bundle is Abp's Theme package bundle + global css bundle. I compared bundled css with previous bundled css, d-lg-block and another css have display:none; in version 8, version 7 has definition for .lpx-login-image-area but version 8 seems not. So I copied version 7 css to local global css.