@nowayja Suite doesn't support Blazor module code generation. sorry!
it's weird.
when you write user it must be filtered to AppUser
did I understand it correct, the localization is not done for OrLoginWith , AreYouANewUser ?
there's this rule; if your appservice / domain service method has seperate business logics which has to be handled seperately then you need to split them into different UOW scopes. Otherwise the complete request will be evaluated as transactional and will be rolled back if hits any exception.
do you see any error logs on your backend side
@prasad.gore sorry for my late response. I might have missed your notification. is it possible for you to switch to the latest preview
dotnet tool update -g Volo.Abp.Cli --version 4.2.0-rc.1
abp suite update --preview
@shobhit, you might be going on the wrong direction. there shouldn't be requirement to change tenant like that. You can redesign it with a different solution. because it breaks major framework rules.
let us know and if it's OK close the issue pls.
it sounds like you need a seperate UnitOfWork scope.
can you create a new UnitOfWork scope to save your changes. (you don't need to manually call the SaveChanges)
https://docs.abp.io/en/abp/latest/Unit-Of-Work#begin-a-new-unit-of-work
hi, first of all this is not a bug or missing feature. ABP CLI is used for both open-source and commercial platforms so, it's not possible to add a commercial feature to the free and open-source tool.
Secondly, you can use ABP Suite via commad line with the HTTP requests. See how you can achieve this https://support.abp.io/QA/Questions/841/How-can-I-use-ABP-Suite-from-command-line#answer-194c035a-d6e7-c34f-5758-39fa4128c977
