I have a view in the DB and a class that I have no problem adding to my DBContext and accessing through a different entity reposittory through the dbsets. But I want to create a repository specifically for this view. But I am unsure the best method for it.
I was thinking just base : Entity with no ID but I have to use a composit keys then and technically I do not have any setup. Any suggestions would be greatly appreciated. Thank you
I have 3 DB contexts, my main one for the ABP API database, two others that connect to two DBs that we already had and all works just fine.
We have one database that has Customer table in it and a Connection table. The Connection table holds DB connections for each customers. This is NOT the main ABP database. But what I want to do is split out Customer specific databses similar to how tenant specific DBs are done in ABP. I want to create a CustomConnectionStringResolver pass in a customer ID to queury the Connection table to get the customer specific DB connection string. Then change the connectionString of our CustomerDbContext to the Customer Specific database instead of the default one. I have done this in other projects that use just basic EntityFramework and no ABL but not that works with ABP and the ConnectionStringNameAttribute. I want to do this with a DbContext that inherits from AbpDbContext<CustomerDbContext> and uses the ConnectionStringNameAttribute.
Any help would be appreciated.
I have been trying to figure out with ABPs Background system how to enqueue to a custom hangfire queue. WIth using just the basic hangfire api I just put an attribute above the method I am calling in the enqueue method [Queue("CustomQueue")] but that does not work with ABPs hangfire version. Is there anyway to get it to enqueue to my custom queue besides the default queue?
I am trying to setup a release pipeline in Azure DevOps for the Angular app to different environments. When I did this with Aspnet Zero I was able to use the appconfig.json file to easily enough do a json replace on the app urls. But it looks like Commercial abp only uses the environment.ts files and I can't use those in the release pipeline because the app is already built at that time.
Basically my question is, How can I reconfigure the app to use a json file instead like how ASPNET Zero does it. I looked at the projects method of how they do it, but wasn't sure how to implement something simular since Commercial abp sets the oAuthConfig and apis url differently. Any help would be greatly appreciated.
Thank you