Removing Features
This template includes many features out of the box. It's designed with the philosophy that it's easier to remove what you don't need than to add it later.
Before You Begin
Before removing any feature, ensure you have your project under source control (Git) so you can easily revert if needed. Also, test thoroughly after each removal.
Before removing any feature, ensure you have your project under source control (Git) so you can easily revert if needed. Also, test thoroughly after each removal.
Authentication Features
- Remove OAuth Authentication - Remove Google, Facebook, and/or Microsoft sign-in
- Remove Multi-Factor Authentication - Remove two-factor authentication (TOTP)
- Remove Self-Registration - Make the app invite-only
- Remove Registration Approval - Allow immediate access after registration
- Remove Password Reset - Remove forgot password functionality
Admin Features
- Remove User Management - Remove admin user CRUD pages
- Remove Role Management - Remove role administration
- Remove Admin Dashboard - Remove the entire admin section
Other Features
- Remove Help System - Remove the help pages
- Remove Startup Validation - Remove configuration validation on startup
General Tips
Order of Operations
When removing multiple features, follow this order:
- Remove configuration settings first
- Remove or update code references
- Delete files and folders
- Clean up navigation links
- Build and test
Finding References
Before deleting any file, use Visual Studio's "Find All References" (Shift+F12) or "Find in Files" (Ctrl+Shift+F) to locate all usages. This prevents broken references.
Database Considerations
Some features store data in the database. Removing the feature doesn't automatically remove the data or database columns. The guides indicate when database changes are needed.