For the MVC pattern, you should put all your logic into the controller.
The view is basically the visual presentation of the data, whilst the
controller, as it name suggests, controls.
There are other thoughts on this. Some say the view can contain small bits
of logic, but I prefer to separate it out as much as possible.
Check out
http://martinfowler.com/eaaDev/PassiveScreen.html,
http://martinfowler.com/eaaDev/PresentationModel.html and
http://martinfowler.com/eaaDev/Super...Presenter.html for the
alternatives.
We are developing our consoles using the MVC pattern. We've made the views
as simple and plain as possible.
All event handling, business logic, import/export, printing etc is done from
the controller.
This should improve the ability to test the controller logic with the view
implementation.
--
Ged Moretta
www.appsense.com
-----------------------------------------------------------------------
This signature isn't automatic. I have to type it manually every time.
"-pb-" <pr*********@gmail.comwrote in message
news:11**********************@k79g2000hse.googlegr oups.com...
We are developing a Windows client using .NET 2.0 and C#. We have
decided to use MVC based architechture due to its obvious advantages.
This application shows data from database in a Grid. We want to add a
functionality of Printing grid and export grid to XL sheet. I would
like to know where will I have to code above functionalities? Should
it be in view or controller?
Any suggestion is well come.
