Hi, the error message System.Net.Sockets.SocketException (10061): No connection could be made because the target machine actively refused it. indicates that the AuthServer application is trying to connect to an SMTP server, but the connection is being refused.
This is likely due to having a wrong SMTP configuration in the application, and since the background jobs run over and over again when there is a problem (retry mechanism), so by any chance, can you check your SMTP configs and ensure they are correct or not?
Hi, first of all, thanks for the quick reply. Great to hear that, the code is working now. For the first question:
You did not answer about migration files? how can we generate migrations for new Entities which are created in Modules? Is it some bug or it should be done always manually? If it is manual process, so what is then reason to pay for Suite... a lot of logic will be in Modules.
ABP Suite creates migrations and applies them to most of the templates. However, for the module templates, since ABP Suite can't know, which module has relation to which main solution, it's hard to get the migration folder and apply it. So, only for the module template, you should create migrations manually, yes.
Hi, can you please confirm that there is a situation as described in this answer or not?
I would like to reproduce the error in a newly generated solution. Unfortunately, I can't find out how to generate a new solution in a specific (old) version using CLI or ABP Studio... how can I do that? Do I need to downgrade the CLI or the Studio first?
EDIT: Ok, I've figured it out... Uninstall the CLI and reinstall the corresponding version. It would be nice if you could also select the version when creating a solution via ABP Studio.
Hi, we have an internal issue supporting selecting a version when creating a solution, but unfortunately could not prioritize it yet. I'll talk with the team.
Regards.
Hi, I guess you are using the default LeptonX Theme. So, if you want to access to the source code, then you can check this link to see how to access to the source code and include it in your solution, if you want.
Also, you can always refer to the LeptonX Theme - Blazor documentation to learn more about the component and see customization tips.
Regards.
Hi, enisn I am not creating migrations. We are using ABP Studio + ABP Suite. I hope it will help to understand our goal: we want to use ABP Suite for creating Entities to be sure all needed code will be generated properly.
Below steps to reproduce issues:
ABP Studio - New Solution [DemoSolution]: Angular LeptonX + EF + SQLite (in prod scenario we will use SQL) + Multi-Tenancy
Solution Created. Build. Run. Works.
ABP Studio - New Module [FirstModule] - DDD Module.
ABP Studio - [DemoSolution] -> Import Module + Install. Graph Build. Run. Ok. And now we want to add new Entites to [FirstModule] module. So:
ABP Suite - version 9.1.0. Selecting FirstModule
Add new Master Entity - [Product] with one property [Title]. Save and Generate. Ok, no errors.
Also I can see [FirstModule] under permissions, and I did grant permissions to admin role. Ok, no errors.
Issue 1 >> I can not find any tables in database. There are no any migrations files create so I can not run dotnet ef migrations list or update database.
Issue 2 >> I can not see [FirstModule] itself on Angular UI. How to manage (CRUD) Product?
Hi, did you check our Modular Monolith Development Tutorial?. In that tutorial, we are explaining important points that you may want to check.
Currently, we also preparing its Angular UI version. To see the related menu items for now, you should write some codes, as mentioned https://github.com/abpframework/abp/issues/20827#issuecomment-2624232973
Please check the tutorial and the issue comment to see if it fixes your problem. Regards.
Hi, can you explain the 3rd step in detail, please? It seems you created an entity via ABP Suite, but I need more details on the entity and if possible complete details to reproduce the problem.
For example, as far as I understand, you have selected the DemoSolution, and then created a Promition entity, right?
Regards.
Everything is working now. Thanks.
Great to hear that. Regards.
Reopenning the question again (it was closed by our support bot). Our QA team tested with PostgreSQL but we could not reproduce the problem.
Can you provide more information to us for reproducing the problem? Unfortunately, currently, we are unable to reproduce your problem.
Regards.
Hi,
Even if I'll set them manually, as you suggest, the repository Update and Delete methods will set them to null.
Yes, you are right. Instead, you can try to change the current principal, which will change the CurrentUser as you stated in the related scope.
We have a section in our documentation for changing the current principal, which you can check out at https://abp.io/docs/latest/framework/infrastructure/current-user#changing-the-current-principal
You basically, need to inject the ICurrentPrincipalAccessor service, and use its Change method (which is a disposable method, so you should create a scope as stated in the documentation) and specify the CurrentUser as you wish. With this way, it should set the CreatorId and DeleterId.
Let me know, if it fixes your problem. Regards.
