C#

Xaotiq wrote:

var dbSets = props.Where(prop => prop.PropertyType == typeof (DbSet<>));

var dbSets = props.Where(prop => prop.PropertyType.IsGenericType && prop.PropertyType.GetGenericTypeDefinition() == typeof(DbSet<>));

var entityTypes = typeof(YourContext)
    .GetProperties(BindingFlags.Public | BindingFlags.Instance)
    .Where(p => p.PropertyType.IsGenericType && p.PropertyType.GetGenericTypeDefinition() == typeof(DbSet<>))
    .Select(p => p.PropertyType.GenericTypeArguments[0])
;

foreach (Type entityType in entityTypes)
{
    DbSet theSet = context.Set(entityType);
    theSet.RemoveRange(theSet);
}

context.SaveChanges();

Richard Deeming wrote:

I don't think there's any easy way to identify the relationships and produce a reliable order for deleting records when cascade delete is turned off.

Introducing FOREIGN KEY constraint '...' on table '...' may cause cycles or multiple cascade paths. Specify ON DELETE NO ACTION or ON UPDATE NO ACTION, or modify other FOREIGN KEY constraints.