Activities of "maksym"
Hi,
I tried using the Inject attribute and it still didn't work.
I've reproduced the error on a clean ABP Solution, here is the link: https://github.com/maksym-gryb/ABPTestSolution
Please try it out and let me know how we can resolve this issue in our codebase.
Hi,
after fumbling around with this feature management module, I found out that it was because we were changing the values via the "Editions" tab, whereas we had to change them in Tenants and use the "Manage Host Features" button.
As we didn't enable multitenancy, nor do we use it, it was rather confusing to know what to look for.
This ticket can be marked as resolved.
I've added virtual and async to the methods but the results are still the same.
As mentioned previously, the issue isn't in the feature management system itself not working, it's the fact that the feature which is set correctly in the database to "true"
Is still being read as "false" in abp via the feature checker
Hi, were you able to reproduce the issue?
Hi, were you able to replicate the issue? Or are you able to get ISettingManager in a module instantiated in an ABP solution?
I was wondering if it could be because it was a long-lived ABP solution and we did a lot of changes to it. But I created a brand new ABP Solution and created a module within that Solution and tried again and still couldn't get ISettingManagement to work in the module.
btw, I used ABP suite to create this module within the solution (both times) using this button:
reopening
Hi, I guess you've created a new module and want to use the
ISettingManageron it, right?If so, please ensure you added the related depends on statement to your module class (ensure your domain module depends on the
AbpSettingManagementDomainModule([DependsOn(typeof(AbpSettingManagementDomainModule))])).
That is correct, I've created a new Module using ABP Suite and want to setup Settings specifically within that module.
I've already added that dependency to the Module's Domain Module:
Yup, that worked!
Thanks for the help!