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.
Microsoft offers two tools and I guess they are thought to solve specific problem. So my question is: what are the key-points that will make me choose one or another technology?
As a subquestion, when you have good knowledge in C# and desktop application but no experience in web application, what is the learning curve of ASP.Net MVC
They are both great platforms and I use both, including WPF. Silverlight, however, may not be receiving a great deal of community/Microsoft support in the future. So you need to factor this in to your decision making process. MVC, on the other hand, has a great deal of support from both the dev community and Microsoft. Plus, it’s been my experience that it’s easier to find MVC talent than Silverlight.
Since you have no or little web experience, the learning curve may be a little tough for MVC. If your desktop experience is winforms, then transtioning to Silverlight will also be tough due to the XAML learning curve. Also, the Silverlight route may aid in the transition to Metro XAML/C# stack, if that’s important to you.
If I was in your shoes and I had to make a decision between the two, I’d opt for MVC.