Sure, big companies still uses WebForms, but what should they to after investing years and years into developing application? Rewrite everything every few years when some new shinny toy comes out?
Sure, big companies still uses WebForms, but what should they to after investing years and years into developing application? Rewrite everything every few years when some new shinny toy comes out?
Companies on the Microsoft stack tend to be extremely conservative. I hardly ever see anyone using these ORMs - I see LINQ-to-SQL or EF, or just as often, inline SQL using DataSets in codebehinds.
I don't think that companies should immediately jump on the next great technology, however there are plenty of companies sitting around on WebForms based on .NET 2.0 (2005) and .NET 3.5 (2007), and a few still on .NET 1.1 (2003). The only reason these companies have not moved onto ASP.NET MVC (or anything else) is because of the sheer cost of doing so. With that comes all of the negatives discussed in the post.