@murat.yuceer
This is fixed. First login to abp.io and then download sample https://abp.io/api/download/samples/easy-crm
see https://support.abp.io/QA/Questions/791
This is because your CLI token has been expired. Relogin with the following command:
abp login <username> -p <password>
I'm getting the following errror.
You are not granted permission to use the module 'XYZ'
@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.
