Activities of "ariandle"

I want to map Features to Organizational Units, similar to how we map Users to Organizational Units.

This works great for adding Users to Organizational Units : UserManager.AddToOrganizationUnitAsync

I want to extend the FeatureManager to also allow this sort of association.

I have created an entity like the example below, but need some advice from here.

[Table("IvFeatureOrganizationUnits")]
    public class FeatureOrganizationalUnit : FullAuditedEntity, IMayHaveTenant
    {
        public const int MaxNumberLength = 16;
        public virtual int? TenantId { get; set; }

        [ForeignKey("OrganizationUnitId")]
        public virtual OrganizationUnit OrganizationalUnit { get; set; }
        public virtual long OrganizationUnitId { get; set; }

        [ForeignKey("FeatureSettingId")]
        public virtual FeatureSetting FeatureSetting { get; set; }
        public virtual long FeatureSettingId { get; set; }
    }

Thanks!

If we don't want to use the .NET Core framework, is there a way to take advantage of Angular 2.0 in the ASP.NET MVC 5.X/SPA project template?

Are you planning upgrading Angular 1.X to 2.0 in that template (ASP.NET MVC 5.X/SPA) in the future?