Forgive me if this is a repeat question. I’ve searched StackOverflow and did not find the answer to my question, so here goes.
We currently have a web application running ASP.NET 2.0 with AJAX Extensions 1.0 and SQL Server 2005 running, is deployed on IIS 6 and developing in VS2005. All works great, but I’m trying to find compelling reasons to migrate. The clients we serve to do not permit plugins in general in browsers, so Silverlight is not a reason for us to migrate. Also, we don’t have any plans to migrate to SQL Server 2008 any time soon and ASP.NET MVC is not in the works either.
Here’s my reasons to migrate. I would like people to comment on them or add to the list:
- I want to work with the newer .NET stuff (and I think other developers would too. Also appealing to prospective employees)
- Want to keep the technology up to date.
- Extension methods
- PageMethods in WebControls
- WCF
- LINQ maybe (we currently use AutoSproc for our DAL)
- ASP.NET AJAX built-in to ASP.NET 3.5 (not really a big deal though)
- VS.NET 2008 JavaScript Intellisense
The javascript intellisense is a huge improvement over anything that’s come before. But at the same time it still fails in some very spectacular ways. All in all a good step but not something I’ve been able to use as much as I’d like.
The extension methods and linq (linq to objects and lambdas, not just linq to sql) are very cool, but since you have an orm already set up you won’t use them as much as you’d like either.
WCF is okay, but you’re probably not going to re-write your existing services for it.
I think the biggest reason up there is keeping your employees happy and attracting good new ones.