Activities of "brauerj@gc.adventist.org"

Ok I found the issue. It had to do with nuget.config. I had an empty nuget.config in that folder and seemingly either copying a correct one or deleting it solved the issue.

Ok I'm getting this error again! Trying to open abp suite on a sub module that WAS created as a sub module to an app-pro project I get this error: "Suite works only with app-pro and module-pro templates!" I've manually added <PackageReference Include="Volo.Abp.Commercial.SuiteTemplates" Version="9.1.3" /> to the SubModule.Domain project which seems to have fixed it previously, but this time is not! This seems to be a REPEATING issue!

I've tried cleaning and rebuilding. I've tried adding [DependsOn(typeof(VoloAbpCommercialSuiteTemplatesModule))], but still same error. And nothing shows in the abp suite logs either. It'd be nice if at least the logs told us what you were looking at to determine "it wasn't app-pro or module-pro."

Jonathan

Ok I was missing a module dependency. All good now

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