[EngincanV] said:
[48949912] said:
[EngincanV] said:
[48949912] said:
[maliming] said:
I will forward to our suite team.Thanks.
Excuse me!
How to Resolve this problem?Hi, the problem you stated is a known problem and we will fix it soon. In the meantime, the only possible solution is to fix it in the generated code. So, manually delete the related line in your automapper class for now.
Excuse me!
How long will it take to fix? The project is urgent. Manual modification is possible, but it's a bit tedious and will require extra time.We have an open issue for this problem and will try to fix it asap, but unfortunately, we can't give an exact time for now.
Could this issue be resolved within this week? It's significantly impacting usability.
[EngincanV] said:
[48949912] said:
[maliming] said:
I will forward to our suite team.Thanks.
Excuse me!
How to Resolve this problem?Hi, the problem you stated is a known problem and we will fix it soon. In the meantime, the only possible solution is to fix it in the generated code. So, manually delete the related line in your automapper class for now.
Excuse me! How long will it take to fix? The project is urgent. Manual modification is possible, but it's a bit tedious and will require extra time.
[maliming] said: I will forward to our suite team.
Thanks.
Excuse me! How to Resolve this problem?
[maliming] said: Great
I found another bug:
First add a new entity and save/generate by ABP Suite V9.3.1
 Then it gives error like this
Then it gives error like this
 It auto add using namespce "using QRSPC.MsaService.Services.Dtos.Shared",but the correct is "using QRSPC.MsaService.Shared",you can see in the green square.
The ABP Suie V9.2.3 is no such issue.
It auto add using namespce "using QRSPC.MsaService.Services.Dtos.Shared",but the correct is "using QRSPC.MsaService.Shared",you can see in the green square.
The ABP Suie V9.2.3 is no such issue.
[48949912] said:
[maliming] said: hi
9.3 will use
MySql.EntityFrameworkCoreby default.You can switch it to Pomelo MySQL
See https://abp.io/docs/latest/framework/data/entity-framework-core/mysql#use-pomelo-provider
Thanks a lot! I will try to replace soon.
Thanks a lot! After switch it to Pomelo MySQL,the problem resolved.
[maliming] said: hi
9.3 will use
MySql.EntityFrameworkCoreby default.You can switch it to Pomelo MySQL
See https://abp.io/docs/latest/framework/data/entity-framework-core/mysql#use-pomelo-provider
Thanks a lot! I will try to replace soon.
[maliming] said: hi
Can you share your test project?
liming.ma@volosoft.com
Thanks.
Excuse me. You can down test project from the link:https://limewire.com/d/C51ZC#qWDI6DGCnZ.
This is the Solution Configuration:
[48949912] said:
[sumeyye.kurtulus] said: Thank you for sharing a project. I have seen that the related library is missing that will correspond to the order service. I am not sure whether it failed to be generated while creating a service on studio, however you can generate the related library using this command
npx ng g @abp/ng.schematics:create-libThe name should be
ordering-serviceYou should sayNoforIs secondary entrypoint?You can let me know if you need further assistance. Thank you for your cooperation.
Excuse me! I Add OrderingService when create microservice solution,
not after create microservice solution.
Excuse me! I found that when I finished create microservice solution ,and then add a custom microservice. after add a custom microservice,then to create angular UI,It‘s succeed. what's the reason?
[sumeyye.kurtulus] said: Thank you for sharing a project. I have seen that the related library is missing that will correspond to the order service. I am not sure whether it failed to be generated while creating a service on studio, however you can generate the related library using this command
npx ng g @abp/ng.schematics:create-libThe name should be
ordering-serviceYou should sayNoforIs secondary entrypoint?You can let me know if you need further assistance. Thank you for your cooperation.
Excuse me!
I Add OrderingService when create microservice solution,
 not after create microservice solution.
not after create microservice solution.

 
                                