Activities of "pablo@ccalp.net"

• ABP Framework version: v7.4.x
• UI Type: Angular
• Database System: EF Core (SQL Server)

I need to use additional functionality of the Azure BlobContainerClient in my project, how can I access it directly without registering another BlobServiceClient in the DI container?

It's working now, thanks.

I did that twice already. Will do it one more time.

I'm currently in 7.4.0, after updating the packages to 7.4.2 the application is no longer running and I'm getting the following errors:

These are the packanges I updated:

"@abp/ng.components": "~7.4.2",
"@abp/ng.core": "~7.4.2",
"@abp/ng.oauth": "~7.4.2",
"@abp/ng.setting-management": "~7.4.2",
"@abp/ng.theme.shared": "~7.4.2",
"@volo/abp.commercial.ng.ui": "~7.4.2",
"@volo/abp.ng.account": "~7.4.2",
"@volo/abp.ng.account.core": "~7.4.2",
"@volo/abp.ng.audit-logging": "~7.4.2",
"@volo/abp.ng.chat": "~7.4.2",
"@volo/abp.ng.gdpr": "~7.4.2",
"@volo/abp.ng.identity": "~7.4.2",
"@volo/abp.ng.language-management": "~7.4.2",
"@volo/abp.ng.openiddictpro": "~7.4.2",
"@volo/abp.ng.saas": "~7.4.2",
"@volo/abp.ng.text-template-management": "~7.4.2",
"@volosoft/abp.ng.theme.lepton-x": "^2.2.2",  

• ABP Framework version: v7.4.x
• UI Type: Angular
• Database System: EF Core (SQL Server)

I'm using a custom error handler implemented per the documentation, and it is working fine, but I'm getting console errors after it handles the errors.

-- In my error handler, I am marking the error as handled and only re-throwing it if not handled:

-- When debugging it I can see that the framework is still wanting to handle the error, but the error is null

<br> -- When it finally gets to the point that it wants to execute, it fails because it can't access the status of the error

Please let me know if this is a bug or if I'm doing something wrong. Also I'm using the AbpAuthorizationException to throw errors but the message is not being received at the client, it just arrives as a 403 I was expecting to see the message I was trying to send back. Thanks.

• ABP Framework version: v7.4.x
• UI Type: Angular
• Database System: EF Core (SQL Server)

I'm deploying ABP to Azure app services, I'm worried that the messages I'm sending using the service bus end up in the staging slot and are processed by an outdated version of my application. I can see in application insights that both my production and staging slots are connected to the same topic. Does the framework already control that or do I have to somehow disable the service bus on the staging slot?

I was having the same issue with Hangfire, but I solved it this way:

    Configure<AbpBackgroundJobOptions>(options =>
    {
        options.IsJobExecutionEnabled = !hostingEnvironment.IsStaging();
    });

Thanks.

Yeah, that's what I have, not sure if there was another way. Do you know how it is handled by the framework, is there any source code I can reference?

• ABP Framework version: v7.4.x
• UI Type: Angular
• Database System: EF Core (SQL Server)

I have created my own custom configuration service and added it to the app.module as a provider:

{
  provide: APP_INITIALIZER,
  useFactory: configurationFactory,
  deps: [ConfigurationService, ConfigStateService],
  multi: true,
},

There are configuration properties that I need before authentication and after authentication, how can I call my configuration service after the user has authenticated to refresh the configuration properties?

I see this being done already by the abp framework, how can I achieve the same?

Thanks.

Thank you, that worked. Is that the recommended way of doing it? I thought that replacing the service would have been the right approach but for some reason, it looks like it was calling my custom class SeedAsync and the framework's SeedAsync method too.

• ABP Framework version: v7.4.0
• UI Type: Angular
• Database System: EF Core (SQL Serve)

I've followed some documents online and looked at the source code for how to replace the PermissionDataSeedContributor but when running the DbMigrator I end up with twice the permissions, one set for the default "admin" role and another set for my custom role.

Here's my code:

using CompuCare.Enums; using CompuCare.Permissions; using Microsoft.AspNetCore.Identity; using System.Collections.Generic; using System.Data; using System.Linq; using System.Threading.Tasks; using Volo.Abp.Authorization.Permissions; using Volo.Abp.Data; using Volo.Abp.DependencyInjection; using Volo.Abp.Domain.Repositories; using Volo.Abp.Identity; using Volo.Abp.MultiTenancy; using Volo.Abp.PermissionManagement; using Volo.Abp.Uow;

namespace CompuCare.DataSeed;

[Dependency(ReplaceServices = true)] [ExposeServices(typeof(PermissionDataSeedContributor), typeof(IDataSeedContributor))] public class PermissionDataSeedContributor : IDataSeedContributor, ITransientDependency {

private readonly ICurrentTenant _currentTenant; private readonly IPermissionDefinitionManager _permissionDefinitionManager; private readonly IPermissionDataSeeder _permissionDataSeeder;

public PermissionDataSeedContributor( ICurrentTenant currentTenant, IPermissionDefinitionManager permissionDefinitionManager, IPermissionDataSeeder permissionDataSeeder) { _currentTenant = currentTenant; _permissionDefinitionManager = permissionDefinitionManager; _permissionDataSeeder = permissionDataSeeder; }

public async Task SeedAsync(DataSeedContext context) { await PopulateAbpPermissionsAsync(context); }

private async Task PopulateAbpPermissionsAsync(DataSeedContext context) { var multiTenancySide = _currentTenant.GetMultiTenancySide(); var providerKey = multiTenancySide == MultiTenancySides.Host ? "admin" : "Administrators"; var permissionNames = (await _permissionDefinitionManager.GetPermissionsAsync()) .Where(p => p.MultiTenancySide.HasFlag(multiTenancySide)) .Where(p => !p.Providers.Any() || p.Providers.Contains(RolePermissionValueProvider.ProviderName)) .Select(p => p.Name) .ToArray();

await _permissionDataSeeder.SeedAsync( RolePermissionValueProvider.ProviderName, providerKey, permissionNames, context?.TenantId ); }

}