dotnet-scaffold-file-handler

To scaffold a .NET file handler, generate a new interface, implementation, DirectoryNames constant, and DI registration. This ensures consistent file-management across modules for groupings like attachments or user uploads in the Core.Logic project.

Before scaffolding a file handler, ensure the DirectoryName mapping matches existing DirectoryNames constants. You also need to prepare a separate UmbrellaFileAuthorizationHandler if authorization is required for the specific file operations.

Yes, you can add optional post-save processing when implementing a .NET file handler. This allows you to perform additional actions such as image resizing immediately after the initial file storage operation completes successfully.

The best way to organize file uploads is to isolate storage concerns into a single scaffolded file handler. This approach generates a dedicated interface and implementation, keeping file-management consistent across different application modules.

No, the scaffolded .NET file handler does not include built-in authorization. It requires a separate UmbrellaFileAuthorizationHandler to manage access control for file retrieval, deletion, and saving operations when needed.

Your scaffolded file handler needs a specific constructor signature to ensure proper dependency injection and integration with Umbrella's storage layer. This enforces consistent initialization and enables the handler to correctly execute storage operations.