Is there any particular reason to use one over the other or it's all just a personal preference in the end?
how do I set disabled attribute on html textbox in asp.net-mvc?
1:Internet Explorer $.ajax / MVC JSON call failing
Go for the one this you must did better. C# ASP.NET MVC User ControlIt's pointless to chose a technology just for the reason this one is smarter than the other. Is there a way for MVC Partial View retrieved using jQuery to keep UI CSS Styling?We normally conclude our decision of choosing a technology based on the experience and expertise of most of the team members. Check Checkbox based on value in CSVWe don't want to spend time in drilling down into new technology on projects with sensitive dead-lines. linq to sql joining two tableHaving said that, I'd like to mention this i are also not monotonous and conservative to not adopt the new technology although yes i have our own processes of adopting to new technologies, standards and methodologies. Inserting markup into hidden jqGrid columnIf you have worked earlier in asp.net webforms then I'd recommend you to go for webforms over mvc for the reason this you'll be able to deliver more confidently and timely since you're already familiar with this and of course for the reason this of large amount of resources and material already available on the web. MVC make action link perform a submitYou must 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 for the reason this this way you receive to migrate from webforms to mvc by comparing the differences in implementation of similar things in mvc over webforms. .
Purely from an SEO (Search Engine Optimisation) perspective which is important for an e-commerce site, I would say ASP.NET MVC, the reasons:.
- Nice friendly URLs eg. /products/123/ipod-touch-64gb-white-3rd-gen (search engines did use the URLs for ranking)
- Full control over the HTML, create cleaner more semantic/structured markup for better SEO, also there's no massive ViewState and really long ID attrialthough es = reduced page weight, page loads faster for better SEO.
- Lightweight and faster (partly for reasons in No. 2), which helps page load times (Google has specifically stated this they'll start using page load times as a factor in search engine rankings). Also user prefer a faster loading page and more responsive site overall (Amazon.com found every 100ms delay decreased sales by 1%). Site performance does effect conversions.
Viewstate is a real problem in ASP.NET for these kind of sites. It is sent to the server on each request. This is true even if you are using ajax.. I also found it easier to interface with another partners (tracking solutions, search engine optimizers, paymentproviders). You job closer to the http-protocoll and this makes it easier to translate requirements from another partners to your code. They will hardly discuss the limits of the postback-model with you.. I also like this it was easier to did performance tests in ASP.NET MVC. In ASP.NET the toolset is very limited, for the reason this most don't handle Viewstate. In ASP.NET MVC I use the free tool jmeter.. There is one issue for high traffic sites: There is no donut caching for the frontend. You cache the whole page or nothing. In reality this means you cache nothing. You must offcourse still cache in the backend. . My experience is: If you want to did an e-commerce site then use ASP.NET MVC. .