It looks like adding this worked
[DependsOn(
typeof(AbpFeatureManagementBlazorServerModule)
)]
Still not sure why it was needed.
Ok now our custom feature group is not showing:
public class IseFeatureDefinitionProvider : FeatureDefinitionProvider
{
public override void Define(IFeatureDefinitionContext context)
{
var myGroup = context.AddGroup("ISE");
myGroup.AddFeature("ISE.IsPersonalEditingEnabled", defaultValue: "true",
displayName: LocalizableString.Create<IseCoreResource>("IsPersonalEditingEnabled"),
valueType: new ToggleStringValueType());
}
}
}
I have two systems. In one the Feature Management shows under settings
In the other I have features defined but Feature Management is missing from the settings screen even with all admin permissions given.
What am I missing? I don't see any reference to Volo.Abp.FeatureManagement in the .Blazor project for the system that works.
Thanks,
Jonathan
[brauerj@gc.adventist.org] said: It looks like I had some missing [DependesOn()] attributes for inter-modular dependencies. Adding those in to see if that helps.
It looks like the missing [DependsOn] attributes were the issue on my side. Adding these has seemingly solved the issue for both applications.
It looks like I had some missing [DependesOn()] attributes for inter-modular dependencies. Adding those in to see if that helps.
Same thing happens with my other ABP Blazor Server app.
It again shows the same types of tasks blocked (completely unrelated application).
I'm wondering if it could be because of some complex interdependencies between modular monolith DDD modules. Does LanguageManagementDomainModule try to use Autofac to create a Singleton Instance and somehow it tries to get instantiated from two sides? If so how would I track that down and prevent it?
I see Autofac.Core.Resolving.Middleware.CircularDependencyDetectorMiddleware.Execute() in the blocked stack...
Sorry how would Blazor development be worth it without hot reload? It's a periodic issue doesn't happen every time... I can try but it might be easier to just start pulling the application apart entirely. But again the periodic nature makes it difficult....
I'm regularly getting a deadlock based hang when starting a debug session (from visual studio). I'm only getting this with some of my larger ABP Blazor-Server apps.
The Console App stops with showing the all of the "Loaded ABP modules." It just never seems to complete the initialization.
Here is the Task View from visual studio. That seems like it should point towards the issue.
Any suggestions on next steps? Often when I restart it will start correctly. The fact that it isn't consistent makes debugging very annoying!
Thanks,
Jonathan
Just as some more feedback. I don't currently find the "custom code" feature useful. I'd much rather have simpler/cleaner code in the first place.
Thanks,
Jonathan
I would be curious to know the reasoning behind the function call approach (vs filter object). I would think the templates should be designed to more EASILY allow direct editing rather than more obfuscation and forcing us to always depend on ABP Suite.
Could you make a community sharing area for templates for ABP Suite? Perhaps as part of the "app store" model being worked on?
I would like a template that does NOT depend on functions on the backend but uses a "filter" object on the back end corresponding to the query DTO currently created on the front end. Then use AutoMapper to map between. I would think that would make a good default/replacement to the current method. Numerous function calls are HARD to maintain!!
I'd make the change myself but it would get out of date too soon and there is no way to share with others so they can help maintain this alternative approach.
Thanks,
Jonathan