Activities of "yekalkan"

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.

https://github.com/abpframework/abp/pull/13059

Hi @jlavallet,

As i see, these logs are harmless and the solution should be created successfully. You can continue development.

We'll try to remove these logs in the next patch version.

Hi @shobhit,

I've saved your feature request. We'll discuss and may include in next releases. Thank you for the feedback.

This is very interesting. See the source code https://github.com/abpframework/abp/blob/dev/framework/src/Volo.Abp.Cli.Core/Volo/Abp/Cli/ProjectModification/NugetPackageToLocalReferenceConverter.cs#L33

We use Directory.GetFiles(...) to find csproj files, and when we try to read one of them we shouldn't receive DirectoryNotFoundException. I don't understand why you are facing this issue.

However, i placed a File.Exist(...) check before reading a csproj file. See https://github.com/abpframework/abp/pull/12768

I'm closing the issue since it will be resolved with that pull request. If you continue to face this issue after stable 5.3 release, you can re-open.

Could you try the same process with CLI?

run this command to create the project:

abp new IWIT.BMSNext -u angular --separate-identity-server --preview

then move to aspnet-core folder and run:

abp add-module IWIT.BMSNext.Dictionary --new -t module-pro --add-to-solution-file

abp add-module IWIT.BMSNext.Basic --new -t module-pro --add-to-solution-file

Hi,

I can't reproduce the problem.

1. Created a project. (IWIT.BMSNext)
2. Added a new module (IWIT.BMSNext.Dictionary)
3. Added an another new module (IWIT.BMSNext.Basic)

It worked successfuly and i could build the whole solution.