Demo Video: https://youtu.be/rJrNwR4Mf7A

This project can be used to create the classes and Blazor components to provide rudimentary CRUD functionality for any table in SQL Server Database, along with the ability to filter and sort.

The classes are all created within this project under a folder called AutoGenClasses, with the intention of moving them into your project.

Primarily it is done this way so that your project no matter how it is configured will not affecct the running of this appllication. Unlike the MVC scaffolding that stops working if you make too many changes in a project.

Your project would require the following to be set up:

1. Automapper will need to be set up in your project.
2. Ardalis.GuardClauses NuGet Package will also need to be installed.
3. When deleting a record created classes will try to call a Blazor component called BlazoredModalConfirmDialog*. This can be found in this project under the Shared folder.
4. Each model will need to exist in your project along with the DB context with the DbSet already added.
5. The Blazor components are set up to use Bootstrap 5 by default.
6. Entity Framework Core.

• If you opt to not use Blazored Modal / Blazored Toast, for compatibility with an MVC application. You will need to copy across BlazoredModalConfirmDialogMVC instead.

Please see the sample application project which contains these dependencies, for more information.

1. Edit the appsettings.json file in the root of DynamicCRUD project. To make the "DefaultConnection" point to your database in SQL Server.

2. Run the application (Do not run watch as the project will crash when it cannot compile the newly created c# classes).

3. Optionally, enter a search term to filter down to a particular table, then select the table in the drop-down list.

4. Click on Populate Columns button.

5. The list of columns should now be displayed. Check the filter checkboxes for each string column that you wish to filter on. Also check each sort column that you wish to sort by.

6. Enter the namespace, this is used to build the namespace for the classes.

7. Enter the singular model name and a plural name. Note the model should already exist in the destination project and be entered in the DB Context.

8. If the primary key is set up correctly the PK Override should not be necessary. However if the primary key has not been set up correctly it may be necessary to use the override. In any case a primary key is definitely required for CRUD operations to be successful.

9. If the table has a parent, you can select a foreign key (One only).

10. Then click Generate C# Classes button, at the bottom of the page.

11. The classes should now exist in the AutoGenClasses folder. Note they will not compile in this project.

12. Copy the code that is displayed red in the webpage into your project, where applicable.

13. Move each file to the required location in your project. Taking care to make sure the namespaces are correct. Build your project and troubleshoot any errors as necessary.

• Model DTO
• Interface and Repository Class
• Interface and Data Service Class
• Model Table Blazor Page Component and Code Behind
• Model Add Edit Blazor Component and Code Behind

In order to make any enhancements or changes to the code or user interface, there are 9 T4 Templates for each of the files listed above.

Only tested with:

• Blazor Server (Not Blazor Client)
• SQL Server Database
• .NET 6/7
• General datatypes like int, long (bigint), bool (bit), DateTime, string (nvarchar) and decimal.
• Now works in a MVC application that uses Blazor project as well.