Activities of "jhsanc"

I have the same problem.

https://support.abp.io/QA/Questions/1233/ABP-Suite-does-not-generate-Blazor-UI-for-a-module

Thank you it's clear not supported yet.

Yes, it is planned to be supported at version 4.4 (https://support.abp.io/QA/Questions/1233/ABP-Suite-does-not-generate-Blazor-UI-for-a-module#answer-b698ced4-ecd2-3b97-2f66-39fc2aaf7e95)

Thank you, then wait.

https://support.abp.io/QA/Questions/1233/ABP-Suite-does-not-generate-Blazor-UI-for-a-module

Thank you it's clear not supported yet.

Hi,

I make an example for you: https://github.com/realLiangshiwei/Qa1129.

Qa module and identity module are two databases

  "ConnectionStrings": { 
    "Default": "Server=(LocalDb)\\MSSQLLocalDB;Database=Qa_Main;Trusted_Connection=True", 
    "Qa": "Server=(LocalDb)\\MSSQLLocalDB;Database=Qa_Module;Trusted_Connection=True" 
  } 

This example it's great, thank you so much.

Hi,

Usually we should not use the entity of another module in a module, it will blur the boundaries of your module.

A good module should focus on its own entities, but sometimes the module needs to read the data of another module. We have the following way:

• Use domain events https://docs.abp.io/en/abp/latest/Distributed-Event-Bus
• Use dynamic HTTI API proxy (reference .HttpApi.Client module) https://docs.abp.io/en/abp/latest/API/Dynamic-CSharp-API-Clients
• Use repository(reference .domain module), In this way, you can read the database directly.

If you really need to share entities between modules, you can define a Entity.Shared project and other modules reference this project. that's ok.

Can you explain me more this "Use repository(reference .domain module), In this way, you can read the database directly". Only add the reference of the project to the project app.

In the generated code of abp framework in DbContext say this: * It does not include entities of the used modules, because each module has already * its own DbContext class. If you want to share some database tables with the used modules, * just create a structure like done for AppUser. * * Don't use this DbContext for database migrations since it does not contain tables of the * used modules (as explained above). See SportsMigrationsDbContext for migrations. But I need know if this is a good practice.

Thank you,

Sorry this not it's a solution from question. I'm going to reformulate my question: For instance for BookStore-Modular: https://github.com/abpframework/abp-samples/tree/master/BookStore-Modular for example. How is the most efficient way to "share" part of "whole database schema" across multiple modules (so that some tables are not defined on application-level but only on module level)?

If application would have the same architecture as BookStore-Modular and part od database would be using the same tables in 4 modules (and other parts of the application - modules don't use these tables at all).

Maybe module, which "holds" tables for modules and each module that should use these tables should reference this "database module"?

I need a shared module which defines the shared entities