Sorry maliming, a bit of issue once again. Would there be problem if I add the additional client web application (said above) after the existing solution complete? The existing solution (with AuthServer, remote service HttpApi.Host and the admin side *.Web project, etc) is near completion.
Thanks Maliming a lot! Great points to take care of.
That is Great! Thanks a lot!
That is good. Let me know if Abp Staff have anything to say or recommend.
I want a physical column to the custom properties. I do not want to store them as extra properties.
How to post the Normal Fields and Custom fields in my custom tab's JS/form?
I want to extend the Identity Users table by adding more profile information. I also want to remove some fields like Surname. Finally, I want to collect the new profile fields in a new tab in the profile editor window.
Thanks! I was also to resort to this approach. If you have any considerations to advice me, otherwise we can close it.
What about using ABP MVC Project Template in the new UI solution? Should I import an existing (another) ABP *.Web project? Can I directly add a new project as ABP MVC Project Template with Basic Theme in the existing solution? How?
How to make the new UI project references/depends on MyCompany.HttpApi.Client so it can use ABP’s generated/typed client proxies to call the existing backend?
