Someone - Please sell me on MVC
-
On to an issue whether or not we should move to MVC development I have been debating this with my developers now for months. And some insist MVC is better though I just dont see it. What makes a programming methodology better for me ? Speed of development. Developer spending less time on interface and normal features and more time getting validation and business logic to be solid Code that is easy to understand by new developers taking on the project Structure that is easy to follow and you dont have to jump between mappings and target pages to check how they link Ability to create reusable controls Visual designer , so you dont have to repeatedly code something as mundane as a table. Scalability When working with MVC4 Razor Visual designer Gone ;( No Server Controls Hooking up an event is manually coded (instead of double clicking or hooking up an event Single controller multiple pages Bottom line is what is quicker , on asp.net I can drag a button on the exact spot i need it double click (3 seconds later) I have a button named and hooked up to an event without touching the keyboard. which the mvc guy is still busy typing his input tag , not to mention switching between the controller and the markup screens creating a event and a model. When i used a aspx grid , I get a nice linq data source hook it up to a grid, columns gets auto generated , meaning all i have to do is change the column headers , click that I want to enable sorting and paging , and I am done 2 minutes later. and if I have not too complex columns the add edit and delete features are created for me in one shot which can be configured for more complex scenarios's Now as an mvc developer doing the whole grid thing , everything has to be coded , I have to code my data queries (be it LINQ or SQL) to do the paging and sorting , 2 hours an insane amount of typing and script later I have something that kinda does the same thing but looks butt ugly. I guess an expereinced MVC dev can do it in probably 10 mintes flat My Recommendation, MVC is ok for cases with little complexity and smaller size projects, but when you need to deliver something of great scale and complexity you are shooting yourself in the foot as you will still be coding interface logic when a asp.net dev is long done with the project. Also just in case you wondering I know 1 MVC does not have viewstate : good practiice minimises viewstate/ you can also hide your viewstate in session using very basic code, also viewstate has never
-
On to an issue whether or not we should move to MVC development I have been debating this with my developers now for months. And some insist MVC is better though I just dont see it. What makes a programming methodology better for me ? Speed of development. Developer spending less time on interface and normal features and more time getting validation and business logic to be solid Code that is easy to understand by new developers taking on the project Structure that is easy to follow and you dont have to jump between mappings and target pages to check how they link Ability to create reusable controls Visual designer , so you dont have to repeatedly code something as mundane as a table. Scalability When working with MVC4 Razor Visual designer Gone ;( No Server Controls Hooking up an event is manually coded (instead of double clicking or hooking up an event Single controller multiple pages Bottom line is what is quicker , on asp.net I can drag a button on the exact spot i need it double click (3 seconds later) I have a button named and hooked up to an event without touching the keyboard. which the mvc guy is still busy typing his input tag , not to mention switching between the controller and the markup screens creating a event and a model. When i used a aspx grid , I get a nice linq data source hook it up to a grid, columns gets auto generated , meaning all i have to do is change the column headers , click that I want to enable sorting and paging , and I am done 2 minutes later. and if I have not too complex columns the add edit and delete features are created for me in one shot which can be configured for more complex scenarios's Now as an mvc developer doing the whole grid thing , everything has to be coded , I have to code my data queries (be it LINQ or SQL) to do the paging and sorting , 2 hours an insane amount of typing and script later I have something that kinda does the same thing but looks butt ugly. I guess an expereinced MVC dev can do it in probably 10 mintes flat My Recommendation, MVC is ok for cases with little complexity and smaller size projects, but when you need to deliver something of great scale and complexity you are shooting yourself in the foot as you will still be coding interface logic when a asp.net dev is long done with the project. Also just in case you wondering I know 1 MVC does not have viewstate : good practiice minimises viewstate/ you can also hide your viewstate in session using very basic code, also viewstate has never
It isn't. The Microsoft implementation of MVC is far (even version 4) from being satisfactory to me too. I'm working on a large enterprise app and before each major version we check what new tools/environments we should use/incorporate. MVC (not the architecture) failed with large noise... I worked with COBOL with the idea of separated layers, but never imagined that 20 years later it will means no code-reuse... I found MVC good only for very small size apps...
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is (V).
-
It isn't. The Microsoft implementation of MVC is far (even version 4) from being satisfactory to me too. I'm working on a large enterprise app and before each major version we check what new tools/environments we should use/incorporate. MVC (not the architecture) failed with large noise... I worked with COBOL with the idea of separated layers, but never imagined that 20 years later it will means no code-reuse... I found MVC good only for very small size apps...
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is (V).
-
Look there are things i like about it , but give it about 2-3 more releases before they have something a bit more commercially viable
Chona1171 Web Developer (C#), Silverlight
2-3 more? after MVC5 of before? It makes if 7-8 releases!!!
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is (V).
-
2-3 more? after MVC5 of before? It makes if 7-8 releases!!!
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is (V).
Never read so much nonsense about MVC framework as I read here. Do you know Stack Overflow? It was written using MVC. Visual Designer? Well, I don't get where it fits on webdesigner/webdevelopment. If you don't know nothing about HTTP and the flow of request/response go with webforms and suffer, suffer a hell in mantainance. You don't like patterns and practices? Go with webforms. MVC is a robust and well known architectural way to build webapps. It shares it concept from the Ruby On Rails. MVC allows low cost mantainance even if the start of the project costs a (little) bit more. Webforms are good for RAD, and IMHO just for that. If you want to build flexible, robust, low mantainance cost webapps despite the complexity of then you will for sure choose MVC.
-
Never read so much nonsense about MVC framework as I read here. Do you know Stack Overflow? It was written using MVC. Visual Designer? Well, I don't get where it fits on webdesigner/webdevelopment. If you don't know nothing about HTTP and the flow of request/response go with webforms and suffer, suffer a hell in mantainance. You don't like patterns and practices? Go with webforms. MVC is a robust and well known architectural way to build webapps. It shares it concept from the Ruby On Rails. MVC allows low cost mantainance even if the start of the project costs a (little) bit more. Webforms are good for RAD, and IMHO just for that. If you want to build flexible, robust, low mantainance cost webapps despite the complexity of then you will for sure choose MVC.
MVC is robust, and well known. The Microsoft implementation isn't - not even close!!! (I tell you a secret - I wrote according MVC 25 years ago in COBOL. No web then!)
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is (V).
