Activities of "mariovh"

Hello,

I don't have a demo solution because we're in the analysis phase and haven't implemented anything yet. I've created a ticket to ask if it's feasible to connect to the database this way, and if there are any design limitations in the framework.

Thank you very much.

We have an ABP.IO multi-tenant application configured as database-per-tenant (each tenant has an isolated Azure SQL database).

We want to avoid SQL username/password in tenant connection strings and instead connect to Azure SQL using Microsoft Entra ID authentication with a Service Principal (Client ID + Client Secret or Certificate).

What we need from ABP support

1. Recommended ABP approach to implement tenant-specific database connections using Entra ID Service Principal authentication.
2. Where to integrate this in ABP:
   • Should we override/implement IConnectionStringResolver (or another ABP extension point) to resolve per-tenant connection settings?
   • What is the recommended place to inject an access token / configure the underlying SQL connection for Entra ID (e.g., during DbContext configuration / connection creation)?
3. If ABP has an official or preferred pattern for this scenario, please share:
   • Docs / sample project
   • or a minimal code snippet showing the correct integration point for Azure SQL + Entra ID Service Principal in a multi-tenant, database-per-tenant setup.

Hi,

My bad, the name convention needed the word Async at the end of function names to work.

Thanks for the support

Hi again,

I partially fixed the parameters error with [FromBody] in AppServiceBase Method

But the response Dto and the implementation still not work:

• ABP Framework version: v9.0.4
• UI Type: Blazor WASM
• Database System: EF Core (SQL Server)

Hi,

I'm having issues generating the static clients using the ABP CLI command.

I have the following AppService interface with its implementation, as well as a base AppService.

Base appservice and methods:

Here is the structure of the DTOs, filters:

This is what the CLI generates with the following command: abp generate-proxy -t csharp -u https://localhost:44393/ --without-contracts

Finally, I'm adding the app-generate-proxy.json file:

And HttpApi.Client references:

Thank you.

• ABP Framework version: v9.0.1
• UI Type: Blazor
• Database System: EF Core (SQL Server)

We are experiencing issues with Blazor WASM initialization due to the loading of modules.

We considered using InteractiveAuto rendering to speed up the initial load of the login page when the user is not authenticated, but this is not an option since our component suite is designed to work with WASM.

We have explored alternatives, such as having two WASM projects referenced from the same Blazor WebApp project (Blazor, Blazor.Client, Blazor.Login), as demonstrated here: https://github.com/jirisykora83/WebAppMultiBlazor

We want to apply this same approach using ABP, with the idea that the additional Blazor.Login project would handle authentication. This project would only include authentication dependencies and the login page to streamline the initial entry into the application.

In other words, when the user is not authenticated, they should be redirected to the login page of the Blazor.Login project. If authenticated, they should be redirected to the Blazor.Client project, which contains all application dependencies and represents the main application.

Would this be possible with ABP? What logic would need to be overridden to achieve this approach?

Thank you very much!

It works correctly, but if I load the application on a page that injects an IApplicationService, when the render mode is Server, it says that it is not registered.

However, if I enter the application through the dashboard and, once the WASM is downloaded, I navigate to the page that has the IAppService, then in Client render mode, it works fine and correctly resolves the dependency injection.

Hello,

I tried updating abp cli, same error:

Thank you

Hello, I created a solution using the command:

abp new Acme.BookStore -u blazor-webapp -m none --theme leptonx -csf

After making changes to BookStoreHttpApiClientModule to use static clients, I ran the command to generate the clients, but I got the following error in the CLI (as shown in the image).

• ABP Framework version: v8.3.2
• UI Type: Blazor WASM
• Database System: EF Core (SQL Server)
• Tiered (for MVC) or Auth Server Separated (for Angular): yes

Hello,

I am experiencing severe startup delays in the WASM application once the WASM assemblies are loaded in the browser.

One of the options we are considering with my colleagues to improve the startup performance of the application after downloading the WASM file is to avoid generating proxies at runtime. Since reflection is costly in WebAssembly, this would save computation time and potentially eliminate the request to the api-definition endpoint, which also introduces a delay.

Would it be possible to generate these proxies at compile time instead?

In a Blazor solution, would this be complex or resource-intensive? Is there any command available in the ABP suite to achieve this?

What would be the recommended steps to follow to enable this feature?

Thank you for your support.