thanks! We'll try that
Hi Engincan, Following up on this question, our project has ~50+ modules being developed by number of developers. We counted on the way ABP Studio makes the modules testable in a standalone dev-app before integrating into the large main app. Could you provide some guidance/sample on how to make it work? I'm noticing that the Issue https://github.com/abpframework/abp/issues/20827 got pushed to v9.3 now. We can't wait for 3 months. Many thanks! Sergei
After some digging in ABP documentation we found that ReplaceDBContext attribute solves the issue.
https://abp.io/docs/latest/framework/data/entity-framework-core?_redirected=B8ABF606AA1BDF5C629883DF1061649A#replace-other-dbcontextes
We can close this ticket now. Thank you!
Hi, could you elaborate please.
Also is there a reason I will get this error?
I already followed pretty much your answer above and I think your sample was not up to date with the latest Abp version as the 'LoginModel' takes in 7 parameter(s) instead of 2
And that is where I met the 2nd exception in the screenshot in the original post
Hi Liangshiwei, Thank you for the suggestion. We've applied it and it worked. Have a great weekend :)
Hello, can I get a response please?
So Creating the entity (backend) in the module (ClinicSaas.Econsent) and generating its UI in the Angular project is not possible with Abp Suite?
Is that correct understanding?
I am sorry I think I confused you.
I am saying, its not generating UI when I try to add a new entity in a module.
Steps:
But UI is giving an error as I mentioned above.
