Mar 04, 2008 02:07 PM|aspevia|LINK
I can think of some very legitimate reasons why it would be a good idea to have controllers in a separate assembly
putting controllers in a separate assembly wasn't the original question. It was putting controllers in the business logic assembly where they clearly do not not belong.
That's a first for me. The "V" in MVC stands for "View" ... which *is* the UI for an MVC application, not the Controller
As to the question about controllers used to create UIs. That's what they are for. Sure the view is the visible UI, but the controller is meant specifically for interacting between the model and the view. Without the view the controller has no meaning
in MVC. In traditional MVC (before the Web variant of it), the controller handled events from the view. In that scenario it could easily be argued that a click event while not a "view" is a UI phenomenon and thus the controller while it may not "be" the
UI, is intimately involved with it.