Is there any particular reason to use one over the other or it’s all just a personal preference in the end?
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.
Is there any particular reason to use one over the other or it’s all just a personal preference in the end?
Go for the one that you can do better. It’s pointless to chose a technology just because one is smarter than the other. We normally conclude our decision of choosing a technology based on the experience and expertise of most of the team members. We don’t want to spend time in drilling down into new technology on projects with sensitive dead-lines. Having said that, I’d like to mention that we are also not monotonous and conservative to not adopt the new technology but yes we have our own processes of adopting to new technologies, standards and methodologies. If you have worked earlier in asp.net webforms then I’d recommend you to go for webforms over mvc because you’ll be able to deliver more confidently and timely since you’re already familiar with that and of course because of large amount of resources and material already available on the web. You can in parallel check and research on asp.net mvc while focusing on your project and start doing small things of your project in asp.net mvc. This is a nice way of transition because this way you get to migrate from webforms to mvc by comparing the differences in implementation of similar things in mvc over webforms.