Activities of "samirmustafayev"

Hi I figured it out. the problem was not in the features. We using RenderdMode so BlazorClient configured to RemoteServer which is the BlazorServer not HttpApiHost.

Thanks.

Any suggestions on this issue, cause dependency is there. Signa R getting the features but by http api it does not?

I could not find solution for the issue that I have

Main project is WASM but modules are Blazor server (they do not have blazorClient). Main project and modules are tiered. Does this endpoint's website depend on your feature definition package? Answers : yes, FeatureManagement modules installed.

Nuget package was made from moduled Blazor WASM project from one of the modules for example Module#2 . MainProject (tiered) Module#1 => (feature groups were added DefinitionProvider) (tiered) Module#2 => (DependsOn Module#1 using adding features to the featureGroup) (tiered) Module#3 => (DependsOn Module#1 using adding features to the featureGroup) (tiered) Module#4 => (DependsOn Module#1 using adding features to the featureGroup) (tiered)

Created New Blazor Wasm moduled tiered project where modules are Blazor server , cause there no BlazorClient. In Domain added FeatureDefenitionProvider with GetGroupOrNull and added feature with default true. In DomainShared added constant for features name to use in BlazorClient MenuContributor class for menu item that RequersFeature().

In database AbpFeatureGroups table the custom added groups are there, also in Administration-Settings-FeatureManagment: FeatureGroups are visible and they functionaly working but in menu they are disappeared

Hi Abp Team,

I am having an issue with the Features in moduled Blazor Web Application. I have a nuget package wich contains FeatureDefenitionProvider for Groups where defenition provider is located in Domain layer and class for const name in Domay.Shared layer, i am using this groups in my modules to control them by features, by default they are true. When i start programm at first every component that is using RequersFeature() are visible, but then disapears on complete program load. As I understand server can see and detect them thas why it visible but when blazor client loads it make them disapear and in abp/application-configuration/feature:values there is no my custom features. My groups are in database with default values and in UI Settings:FeaturesManagement: groups and children are also visible and working. For example i will show featuresdefenition provider for Saas: Domain

using Payhas.Billing.Platform.Localization;
using Payhas.Common.Features; // this is the nuget package
using Volo.Abp.Features;
using Volo.Abp.Localization;

namespace Payhas.Billing.Platform.Features;

public class SaasFeaturesDefinitionProvider : FeatureDefinitionProvider
{
    public override void Define(IFeatureDefinitionContext context)
    {
        var mainModuleGroup = context.GetGroupOrNull(ModulesFeatures.Main);

        mainModuleGroup?.AddFeature(SaasFeatures.Saas,
           defaultValue: "true",
           L(SaasFeatures.Saas));
    }

    private static LocalizableString L(string name)
    {
        return LocalizableString.Create<PlatformResource>("Features:" + name);
    }
}

DomainShared:

using Payhas.Common.Features;
using Volo.Abp.Reflection;

namespace Payhas.Billing.Platform.Features;

public class SaasFeatures
{
    public const string Saas = ModulesFeatures.Main + ".Saas";

    public static string[] GetAll()
    {
        return ReflectionHelper.GetPublicConstantsRecursively(typeof(SaasFeatures));
    }
}

Blazor.Client: Navigation MenuContributor

//Saas
 var saas = context.Menu.GetMenuItem(SaasHostMenus.GroupName);
 saas.RequireFeatures(SaasFeatures.Saas);

<br>

Thanks for responding. )))

But with change of configuration, does the localhost also should change in browse as entry point. You still using localhost:44336, instead of test.company:44336? Or am I misunderstanding?

No, I ment url not port

{
  "App": {
    "SelfUrl": "http://test.company:44336"
  },
  "AuthServer": {
    "Authority": "https://localhost:44376",
    "ClientId": "Billing_Blazor",
    "ResponseType": "code"
  },
  "RemoteServices": {
    "Default": {
      "BaseUrl": "https://localhost:44317"
    },
    "AbpAccountPublic": {
      "BaseUrl": "https://localhost:44376"
    }
  }
}

Hi, yes it is working. It overriding it. Try to change localhost to random url. In api it works, but in blazor it does not work. Thanks.

Thanks, will wait for your responce.