Ok i found the problem and solution. I actually changed the feature to have multiple features but forgot to add them to default edition. After i added them in DefaultEditionCreator class, it worked. Thanks!
I am not so sure how to use this attribute correctly: DefaultDbContextAttribute. Do I need to apply them to all bounded contexts i have or something else?
How do i get this update since I only use the library from Nuget-Packages?
Hi!
Basically, for each module, i have a Core, Application, Mapping, and a Bounded Context (No Migration). Below are the contexts i have:
1- Project DBContext: this project DBContext is not used as a reference in any coding projects. It is used for migrating a project as well as creating fake dbcontext in testing only. This DBContext will contain all mapping entities for a project and used to keep track a project database migration and version.
2- Common DBContext (Bounded Context): this bounded context carries ASP Zero and those common/sharing entity mappings only. It inherits from from AbpZeroDbContext<Tenant, Role, User>. This dbcontext does not have migration .This project also contains a repository implementing IRepostory. This is referenced in ASP Zero Application, Core, Web API, and Web. This DBContext has a following static constructor:
static CommonDbContext() { Database.SetInitializer<CommonDbContext>(null); }
3- Module DBContext (Bounded Context) : Each module will have a dbcontext containing only entity mappings related to the module. This context is inherit from AbpDbContext. It does not have any migration file. Since each module has its own applicatoin and core project. This module bounded context does not have any repository implementation. This context is referenced in its own Core and Application projects as well as Web Api and Web project. It also has a static dbcontext:
static ModuleADbContext() { Database.SetInitializer<ModuleADbContext>(null); }
For these codes, It worked in the version 0.8.2.0. I only used 1 Repository implementing in CommonDataContext. For those other bounded context for each individual module no need to have the custom or extra repository. I used IRepository in all application service implementations. ASP Zero was smart enough to use the right dbcontext based on the entity i used. However, after upgrading to 0.9.3.0, I have errors with "Found more than one concrete type for given DbContext Type".
So, yes please let me know if there is a way that i can avoid creating custom repository for each module i have.
Hi! I also have the problem of "Found more than one concrete type for given dbcontext type" after I upgrade from 0.8.2.0 to 0.9.3.0. Actually, I use DD design and i have many bounded contexts based on modules i have. Those bounded contexts uses only one single database or one connection string. For 0.8.2.0 version, I can do it without any problems and no need to define a custom repository since different bounded contexts contain different entities mapping and ASP.NET Zero design is smart enough to use the right bounded context. Here, i would like to confirm, for version 0.9.3.0, do i need to define each custom repository for each bounded context i have or is there anyway I can still enjoy using one repository for all bounded contexts?
Thanks!
I try to extend timeout and save all 20,000 records at once but it seems much slower than saving or instantiating new unit of work for every 1,000 records.
I saw people talking about bulkinsert extension but I am wondering how or where I can apply it with ASP.net Zero since I do not explicitly instatiate the context? I use unit of work and repository as illustrated in the asp.net zero examples.
Hi!
Can you let me know how to how to inject Dynamic routes from abp (DynamicApiControllerBuilder) into the HttpSelfHostConfiguration?
Best