Would creating a controller's interface a bad idea? I have a controller that derived from ApiController, so knowing that you can only derived one class to a class but able to derived one or more interface to a class.public class FooController : ApiControllerMy problem is I have code that is in another controller that can be used in FooController. I don't want to repeat the code so I'm thinking to create a base class that will hold common codes and create an interface for the base class. Would this be considered a bad idea or any suggestion on this?
ASP.NET: Creating an interface for a controller
c#;asp.net mvc;interfaces;class