As an instructor of NET Framework 4 that uses Visual Studio 2010, ASP.NET is under-the-hood object patterns.  C# is the best language to use since it designed to be compatible with NET Framework 4 and so is SQL 2008 and Server 2008 with Active Directory using Federation features.  Any MS versions less than these are going to be phased-out because the earlier software versions were a bit of a batch job because all the Federation and NET Framework 4 collaboration features were not fully compatible within the same object pattern technology (based on C# features).  Hence, this most currently implementation level now supports all Federal design goals; the federation feature allows MS to use one architect/framework that achieves single one logon for the Internet doing away with dealing with intranet and extranet configurations.  This was and has been Gates’ vision for over a decade.

There will be fewer and fewer radical changes in the architecture unless a sever design fault is discovered.

ASP.NET is a facade build on object patterns to keep the millions of small developers under the MS family marketing umbrella.  Under-the-hood the object pattern inventory services were built to support patterns like MVC, MVP, SOA, and other more advanced object patterns.  ASP.NET will die on its own being replaced by the newer generation of programmers while attempting to assist the older ASP.NET style programmers to move to MVC.  MVC is more robust, easier and faster program as well as less fragile.  Therefore, the best moves are to build using Visual Studio 2010 with C# and NET Framework 4 using MVC object patterns.  This way you will be OK in 2 years when Microsoft will move away from supporting ASP.NET (or just won’t enhance its features).

I have moved to include the SOA service design software such as (WF) Work Flow and (WFC) Windows Communication Foundation since these are used to create Internet facing transaction applications that can be Cloud enabled.  More fun stuff.,,

Follow discussion on Forums.ASP.NET