2

At http://www.codeproject.com/Articles/552846/Why-s-How-s-of-Asp-Net-MVC-Part-1, I read this: "You should not use Asp.Net MVC if you rely on 3rd party vendor controls for of the UI."

The author doesn't seem to say why (maybe the explanation is too subtle, or I'm too dense). Thoughts? Is it true? Why would this be?

3
  • 1
    This is my personal opinion: In general, codeproject.com has some weird, untrustworthy content. You should not avoid asp.net mvc because of third party UI controls, that refers to WebForms UI controls which should be irrelevant if you don't know what they are anyway. Today ASP.NET is very competent and powerful technology. – Benjamin Gruenbaum Jul 2 '13 at 22:51
  • 1
    Oh, I see, he probably was talking about those "dragon drop" controls. – B. Clay Shannon Jul 2 '13 at 22:54
  • Yes, those are the ones -_-. With big sites (like this one!) using Asp.NET MVC I think you have nothing to worry about. – Benjamin Gruenbaum Jul 2 '13 at 22:55
2

Not true. Such frameworks are an example how ASP.NET MVC can be used in adjunction with 3rd party controls, also implemented the ASP.NET MVC way (HtmlHelper extensions).

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.