Activities of "alper"

@dmeagor

Updating nuget packages - Suite

1-Created a new project with version 4.0.2

2-Clicked "Update all ABP packages"

3-I see the versions are updated to 4.1.0

check that you have both CLI and Suite updated to 4.1.0. otherwise I don't see a reason not updating to 4.1.0 :/

New module creation - Suite I reproduced this issue. created an issue. will be fixed in 4.1.1. for a workaround use the CLI. it'll create the host folder. then you can add this module to your solution (or just move the host folder)

abp new Acme.MyProModule -t module-pro

angular proxy multiple issues reported by my developers. can you provide a concrete issue so that I can report to the team?

Please, slow down! thanks for your suggestion ;)

When you create a monolithic application, then you can use the AppServices as WebAPIs. But in tier layout it's not available. This is a diagram of a sample microservice (tier).

Explained here https://docs.abp.io/en/abp/latest/Best-Practices/Module-Architecture

@jackmcelhinney will be fixed in the next version.

module is a sub application and it shouldn't be decided to expose all appservices in the module.

hi,

first of all I advice you to do this long lasting operation in a background job. https://docs.abp.io/en/abp/latest/Background-Jobs For example you can use HangFire ...

your first approach is not feasible. working with bulk data needs to be going out of the rutin rules. in this point, you can run a Stored Procedure or run a custom executable or you can completely write a new console app with Dapper to run your bulk operation.

In your 1st approach you can disable transaction. see this document . but it's not practical to iterate over 40K records.

 [UnitOfWork(IsDisabled = true)]
        public virtual async Task FooAsync()
        {
            //...
        }

my advice can be Stored Procedure, pass the parameters to Stored Procedure and you can make it transactional in your Stored Procedure. see this stored procedure sample.

@developer1 thanks for your feedback. yoru reported issue has been already fixed in 4.1.1.

there are 3 database providers (EF Core, MongoDB, Dapper) * 3 Front-Ends (Angular, MVC, Blazor) * Tier/Seperated IDS4 structures. Maybe you are working on one project type, but there these different projects ( cartesian of these options ) it's hard to test all the variants.

On the other hand, the team is setting up a UI testing devops line now with Playwright We are very close to finish this testing environment. We'll be testing different variants of ABP after each preview. So I hope these issues will be less or zero. Thank you for your understanding.

if you get "You are not granted permission to ....." then means your token has been expired. Try to login again.

run this to update

dotnet tool update -g Volo.Abp.Cli && abp suite update

also you need to update your packages to 4.1.0

@trendline do you still get license error?