Base solution for your next web application

Activities of "moetarhini"

I am working on AspNetZero Core with Angular 8. I have read a lot of articles about using composite sql key for muti-tenant systems. It will keep the data consistent and retain the data integrity concept. It will save a lot of validations when you insert entity with related items (IDs). So no need to check if those IDs is owned by the current tenant. It will be maintained by Sql Server. If we decided to use it, is there any compatibility issues with AspNetZero framework?, since someone mentioned that he had an issue with soft delete: https://support.aspnetzero.com/QA/Questions/1378 what are your recommendations about this technique?

I am using Aspnetzero framework with Angular 8. when I add new entity that implements IMustHaveTenant the TenantId is added to the entity table but the foreign key constraint is not added. My question is should we add this constrain for data integrity with AbpTenant table or not?. If yes what is the best practice to add it.

Question

Hello Support,

How can we enable Users to Define User Defined Fields at Run Time and make those Fields available in the UI Forms?

Also, can we expose those Fields to the Listing Pages where you show for example the List of All Users? Can they see the UDF Fields in the List as well and how?

Regards,

I have created a new user-related setting and added it to the AppSettingProvider as new SettingDefinition. I am able to save the setting values to the database and retrieve them on the server side, but the JSON object returned from abp.setting.values does not include my custom settings.

Also, the settings seem to be not loaded when I try to access them in the _layout.cshtml, is this the correct behavior? Is there a way to access settings values in the _layout page?

Thank you

Hi,

We are trying to create a project based on ASPNET Zero module, and we need to use Custom Repositories for our Models. We used the built-in DI mechanism to inject this repository in the Domain Service, and then call it in the Application service. However, We are getting this error "Declaration referenced in a method implementation cannot be a final method." in the Castel Windsor library (DynamicProxyGenAssembly2).

Is this a familiar issue faced before? We followed the following link for guidance [http://www.aspnetboilerplate.com/Pages/Documents/Repositories]) Section: Custom Repositories

[http://www.aspnetboilerplate.com/Pages/Documents/EntityFramework-Integration#DocCustomRepositoryMethods])

Thank you Moe

Showing 1 to 5 of 5 entries