Activities of "enisn"

Hi @balessi75

You can't reference any application layer in the domain layer. That violates DDD and also it's a circular dependency. If you have to add a validation to a DTO you can define it in Application.Contracts layer. You should use AppService interfaces since they're placed in the same layer and the runnable end application registers their implementations if it's a client proxy or application service instance.

As a note, if you convert your project to tiered or micro-service architecture, you have to know that appservice interface implementation will be replaced with client proxy implementation and it'll make a HTTP request for each usage.

Hi @LinchArnold

We've investigated and verified the issue. In the module-pro template, sample/test projects are not the real applications, they're just for testing your custom module. If your module is dependent on the account module or you develop something related to the account module, you have to add the account module reference to your project. By doing it, you'll see the account permissions and that setting tab in your application.

If your module doesn't depend on the account module but you still want to see the account in that test project, you can apply the following steps:

1. Add Volo.Abp.Account.Pro.Admin.Application.Contracts to the IdentityServer project.
2. Add dependson attribute in IdentityServer module file.

   typeof(AbpAccountAdminApplicationContractsModule)
   

3. Clear Redis keys (If it runs on docker, you can remove the volume and re-run again)
4. Re-run application. (Make sure IdentityServer is built after adding reference.)

Then you can see account permissions and the account tab on the settings page.

Hi @AdamMusson

I'm trying to reproduce this issue and I have some questions about it?

• Did you create a new service with the name CategoryService?
• Is your Category entity and appservice in ProductService or your newly created service?
• Is the URL https://localhost:44725 gateway's URL or the newly created service's url?

We released v5.2 but this couldn't be shipped in v5.2 version, it'll be available very soon in the next patch version

In your json, type seems as string and value is "FontAwesome but it should int and values should be 0 and 1.

Most probably you've made a customization for json serializer such as serializing all enums as string in your project that affect the entire project.

Make sure ABP endpoints aren't affected that configuration if you have.

Hi @balessi75

I've confirmed the issue and we'll fix it in the next patch version of v5.2.

Thanks for your feedback, you question will be refunded (if available) since it's a misimplementation of some datagrid columns

Hi @cezary.bojko

Most of the file extensions have predefined font awesome icons. Icon definitions are separated with FileIconType enum that has 2 members such as FontAwesome and Url. All the predefined icons are defined as Fontawesome. So, font awesome classes shouldn't be placed as image by default if you don't override or configure icons for file management module.

Do you have any custom configuration in your application for File Management module? (at the backend, in C# side)

Hi @bozkan

IBlobContainer is an abstraction over different providers and it contains only common operations. So currently, there is no GetListAsync (or something equivalent) method.

You can manage your files with File Management Module. That module still doesn't get the list from the blob provider but it saves metadata about files in application storage and provides a system to you for managing your files.

As I see, this is a typical Redis timeout error. If the redis is deployed to a different server, that means you have to transfer entire data from redis to app, or app to redis and with 1000 count of data it might be costful. You can configure a bigger timeout value for redis or optimize the data that you transferred.

I can't find an exact answer for that. I don't know how you use the Redis. You can share Steps to reproduce the issue or provide a sample project so we can investigate if the problem is related to ABP or not but it seems it's not related to ABP, it seems it's a common Redis usage issue.

Hi @Buckoge

So far, I have successfully solved everything through documentation or through posts, now i need your help so I can upgrade to the new version

Example 4.4.4

As you can see in the picture, the loading time is 3.18 s

Example 5.1.3

As you can see in the picture, the loading time is 10.77 s

As an answer to performance issues, we can't say anything according to this comparison. Request-response time can be affected by many things including network bandwidth or server throughput or etc.

If you have any benchmark result that clearly shows the problem is related with ABP Framework, then we can take some action. Otherwise, we never know where the problem is.