Activities of "yekalkan"

@besquare

I created a project with the same name, then replaced the DbContext file with the one you sent. Then i generated an entity via ABP Suite and it worked as expected. No error occurred. (Windows 10)

I can suggest these:

• Remove the project from ABP Suite, and add again. (Windows 10)
• Check if there is any other file that ends with *DbContext.cs postfix. If so, please send it to us.
• Continue using ABP Suite on OSX until we find a solution to this problem.

@Katherine

Thanks you. We'll try to reproduce the issue asap.

@besquare

In the previous reply i asked you to share the *DbContext.cs file 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 @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

@Katherine

Are there any error logs on the browser console?

Can you share the full logs?

2022-06-28 09:17:27.100 +02:00 [ERR] Expression expected

This seems cut.

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 @manuel42,

Can you share the application logs? What is the exception that is caused the internal error message?

Also, be sure to use 5.2.2 version of ABP Suite if your solution is 5.2.2.

Hi @besquare,

We're checking the issue.

Hi @ageiter,

Thanks you for the feedback. We'll create internal issues about those and fix it in the future releases.

I've refunded your question credit.