How bad are default controllers in ASP.NET MVC???

Question

ASP.NET

Well, we created controllers, they use the same repository already created thanks to DbSet, it has all the checks for values, especially if you use EntityFramework or any other + Annotations to firstCode, for validation.
What are their pros and cons, are there any???
After all, they do whatever is necessary.
And yes, if it's not an EntityFramework?

Answer 1

Depends entirely on your task. Here you did something. If it suits you completely, everything works as it should, "they do everything that is necessary" then the controllers and other things are excellent. It may turn out that the project will grow and become more complicated. When default controllers + EF without additional layers of abstraction stop "doing everything you need", but on the contrary, they will only complicate your life. Then you yourself will understand how and why they are bad. Until then, there is absolutely nothing wrong with them.