Hi Halil,
I found out that there is a circular dependency exception, look below:
WARN 2016-04-04 12:41:48,339 [56 ] Default - Exception when resolving optional dependency Dependency 'FeatureValueStore' type 'Abp.Application.Features.IFeatureValueStore' on component Abp.Application.Features.FeatureChecker. Castle.MicroKernel.CircularDependencyException: Dependency cycle has been detected when trying to resolve component 'EZ.EZControl.Authorization.Users.UserManager'. The resolution tree that resulted in the cycle is the following: Component 'EZ.EZControl.Authorization.Users.UserManager' resolved as dependency of component 'EZ.EZControl.MultiTenancy.Demo.TenantDemoDataBuilder' resolved as dependency of component 'EZ.EZControl.MultiTenancy.TenantManager' resolved as dependency of component 'EZ.EZControl.Editions.FeatureValueStore' resolved as dependency of component 'Abp.Application.Features.FeatureChecker' resolved as dependency of component 'Abp.Application.Features.FeatureDependencyContext' resolved as dependency of component 'EZ.EZControl.Authorization.Users.UserManager' resolved as dependency of component 'EZ.EZControl.Authorization.PermissionChecker' resolved as dependency of component 'EZ.EZControl.Web.Controllers.ApplicationController' which is the root component being resolved.
Here is the complete log file:
[https://portalvhdsdtx1sqp9m14cf.blob.core.windows.net/vhds/Logs.txt])
Is this a known issue?
Thanks
1 Answer(s)
-
0
Thanks for your report. Yes, we know it (<a class="postlink" href="https://github.com/aspnetboilerplate/aspnetboilerplate/issues/934">https://github.com/aspnetboilerplate/as ... issues/934</a>) and will fix it with the next ABP framework release. And after you upgrade nuget packages, it will be fixed.
Thanks.
