thank you we got your dbcontext file and respond you asap.
Any update or workaround to resolve this? We're stucked on project from about a week.
@besquare
In the previous reply i asked you to share the
*DbContext.csfile with us.I couldn't reproduce the issue. Can you share the *DbContext.cs file with us? You can send it to support@abp.io mail address.
I suspect it is related with file character encoding (utf-8, ascii, unicode etc.). But i can't be sure unless i check the original file.
Hi sent email with DbContext.cs
Hi @besquare,
The lines related with Payment module is not added by ABP Suite. 5.2.0 template already have them. But in 5.3.0 version these lines are removed because the template no longer depends on Payment module.
Actually the Saas module no longer depends on the Payment module in 5.3.0 version. So after the ABP Suite updated the dependencies, Payment dependency is lost. That is the issue you are facing.
Check the migration guide: https://docs.abp.io/en/commercial/latest/migration-guides/v5_3
Ok thanks you cleared the question about migration, but what about the abp suite for Entity generator? Why is not more working?
Hi again @besquare,
I couldn't reproduce the issue. Can you share the *DbContext.cs file with us? You can send it to support@abp.io mail address.
Also i've found an issue when upgrading project modules from 5.2.0 to 5.3.0 where a reference 'Volo.Payment.EntityFrameworkCore' was wrongly added to {ProjectName}DBContext.cs into EntityFramework project. We're not using any Payment and ConfigurePayments() fail during build.
Do you use Payment module in your solution? Also, how did you upgrade the solution?
Hi @yekalkan,
No payment module in not added in our solution but after upgrade from 5.2.0 to 5.3.0 using abi suite the module are added automatically into EntityFramework Project.
I've commented out. Bug is reported also if i'm trying to update both from OSX or Windows.
Issue is still not resolved. We're totally stucked into add new Entities.
There's any workaround i can try?
I think the tool is some quite unstable. Sometime create entity only on .NET Core but not on Angular.
Now we've setup from scratch a Windows 10 Development machine with Visual Studio 2022 and NodeJs npm v 8.5.5 node v 16.15.0
Hi @besquare,
We're checking the issue.
Hi @yekalkan, there's any update on this? Because on Windows 10 we're unable to generate any new Entity.
Also i've found an issue when upgrading project modules from 5.2.0 to 5.3.0 where a reference 'Volo.Payment.EntityFrameworkCore' was wrongly added to {ProjectName}DBContext.cs into EntityFramework project. We're not using any Payment and ConfigurePayments() fail during build.
Thanks.
[10:34:36 ERR] ---------- RemoteServiceErrorInfo ---------- { "code": null, "message": "An internal error occurred during your request!", "details": null, "data": {}, "validationErrors": null }
[10:34:36 ERR] StartIndex cannot be less than zero. (Parameter 'startIndex') System.ArgumentOutOfRangeException: StartIndex cannot be less than zero. (Parameter 'startIndex') at System.String.Substring(Int32 startIndex, Int32 length) at Volo.Abp.Suite.Areas.AbpSuite.CrudPageGenerator.Commands.EntityGenerateCommand.ByZHdBwGMk(Boolean , String , String ) at Volo.Abp.Suite.Areas.AbpSuite.CrudPageGenerator.Commands.EntityGenerateCommand.qu6HxKnaPR(Boolean ) at Volo.Abp.Suite.Areas.AbpSuite.CrudPageGenerator.Commands.EntityGenerateCommand.vAiHC7P35n() at Volo.Abp.Suite.Areas.AbpSuite.CrudPageGenerator.Commands.EntityGenerateCommand.ExecuteAsync(CrudPageCommandOptions options) at Volo.Abp.Suite.Areas.AbpSuite.CrudPageGenerator.CommandManager.ExecuteAllAsync(CrudPageCommandOptions options) at Volo.Abp.Suite.Areas.AbpSuite.CrudPageGenerator.Commands.CrudPageGenerator.GenerateAsync(EntityModel entity, Solution solution) at Volo.Abp.Suite.Controllers.CrudPageGeneratorController.SaveAndGenerateEntityAsync(Guid solutionId, EntityModel entity) at lambda_method1792(Closure , Object ) at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.TaskOfActionResultExecutor.Execute(IActionResultTypeMapper mapper, ObjectMethodExecutor executor, Object controller, Object[] arguments) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.<InvokeActionMethodAsync>g__Awaited|12_0(ControllerActionInvoker invoker, ValueTask`1 actionResultValueTask) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.