I'm trying to re-use the controller. Forget ASP.NET for a moment. I have two interfaces to the same application. One if WinForms (let's say) and the other is ASP.NET. My purpose for using MVC is to re-use the controller.
When someone logs in using a web page, the application should validate the user and if so display the main menu. Why should i re-write this logic for WinForms/ASP.NET? I can just make sure my views implement specific interfaces and that way I leave all
the control in the hands of the controller.
frparel
0 Points
15 Posts
Re: MVC Architecture
Dec 11, 2007 08:19 AM|LINK
I'm trying to re-use the controller. Forget ASP.NET for a moment. I have two interfaces to the same application. One if WinForms (let's say) and the other is ASP.NET. My purpose for using MVC is to re-use the controller.
When someone logs in using a web page, the application should validate the user and if so display the main menu. Why should i re-write this logic for WinForms/ASP.NET? I can just make sure my views implement specific interfaces and that way I leave all the control in the hands of the controller.
Am I entirely missing the point?