Activities of "aaron"

Define an event handler:

public class IntegrationDeletingCascader : IEventHandler<EntityDeletingEventData<Integration>>, ITransientDependency
{
    private readonly IRepository<IntegrationStep> _integrationStepRepository;

    public IntegrationDeletingCascader(IRepository<IntegrationStep> integrationStepRepository)
    {
        _integrationStepRepository = integrationStepRepository;
    }

    [UnitOfWork]
    public virtual void HandleEvent(EntityDeletingEventData<Integration> eventData)
    {
        var deletedIntegration = eventData.Entity;
        _integrationStepRepository.Delete(e => e.IntegrationId == deletedIntegration.Id);
    }
}

Delete the bin folder in your Web project and rebuild the solution.

You can define the css like this:

organization-tree > div {
    height: 400px;
    overflow: auto;
}

Can you check the error log in *.Web.Mvc\App_Data\Logs?

You can add this attribute to your methods: [WrapResult(WrapOnSuccess = false, WrapOnError = true)]

Cookies are not cross-domain. That would be a security disaster.

Nope. AFAIK there's no direct way to discover cascade relationships. Also, the purpose of cascading is for data integrity when hard-deleting. Since soft-deleted data is still there, not everyone may want to cascade that delete. So it's more reasonable to do this explicitly. Related issue: https://github.com/aspnetboilerplate/aspnetboilerplate/issues/1992

Are those entities soft-deleted? If so, you need to cascade soft deletes yourself.

If you read my link on EF Core Database Providers, you would know that EF Core doesn't support NoSQL databases. It is also unlikely for AspNet Zero to go huge into NoSQL.

See this link for Azure Cosmos DB: https://docs.microsoft.com/en-us/azure/cosmos-db/documentdb-dotnetcore-get-started

You already posted about this: https://forum.aspnetboilerplate.com/viewtopic.php?p=23348