Rider displays rollback warning when EF Core migration lacks a Down method

Direct answer

Rider does not automatically generate a Down migration, nor does it block the rollback action. Instead it displays a warning dialog that requires manual confirmation when the selected migration class has no Down method or the Down method throws NotSupportedException. This approach balances safety with workflow convenience.

Likely explanation

The warning is triggered because Rider cannot verify that the migration is reversible. EF Core treats a missing Down method as an indication that the migration may cause data loss if rolled back. Rider therefore prompts the user to acknowledge the risk before proceeding.

Confirmed facts

• If a Down method exists and contains only reversible operations, Rider allows rollback without additional warning.
• If the Down method is absent or throws NotSupportedException, Rider shows a confirmation dialog warning of possible data loss.
• Rider provides no setting to auto‑generate Down migrations or to disable this warning.
• The behavior is intended to prevent accidental destructive rollbacks while still letting experienced developers override the warning when they know the operation is safe.

Steps to observe the behavior

1. Create an EF Core migration that overrides only Up (no Down method).
2. Build the project.
3. Open Rider’s Database tool window, navigate to the migration, and click Rollback.
4. Observe the warning dialog that asks for manual confirmation.
5. Add a proper Down method that reverses the Up changes, rebuild, and repeat the rollback – the warning disappears.
6. Replace the Down method body with throw new NotSupportedException();, rebuild, and rollback – the warning appears again even though a Down method exists.

Recommendation

Keep the current warning‑and‑confirmation approach. It protects against unintended data loss without hindering productivity, and it aligns with EF Core’s expectation that developers explicitly provide reversible migrations when needed.

One missing diagnostic detail

If you know that the migration contains only additive, schema‑only changes that are inherently safe to reverse (e.g., adding a nullable column), please confirm whether you would still like Rider to suppress the warning in such cases; this would change the recommendation toward a more permissive setting.