Now that ASP.NET MVC has had its official release, should I be looking into it for my team?
We’re quite a small team (6 developers), developing mainly in-house applications for administrative teams.
Any, and all, advice is appreciated.
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Now that ASP.NET MVC has had its official release, should I be looking into it for my team?
We’re quite a small team (6 developers), developing mainly in-house applications for administrative teams.
Any, and all, advice is appreciated.
It is definitely worth looking into, most things are. Create a few test applications to get a feel for it and to see if it is a good fit for your team and the types of projects you work on.
Remember that there is no such thing as a silver bullet and not all tools are meant for all projects. MVC (in general, not just specific to Microsoft’s ASP.NET implementation) is a nice way of developing certain types of applications but it can be a pain to use in the wrong situations (i.e. sites that use forms for data entry with lots of fields). As in all things remember that ASP.NET MVC is just another tool in your workshop.
As a final note I would strongly suggest that you include your whole team on the evaluation of ASP.NET MVC as you want to make sure that everyone likes and is comfortable using the new platform.