This document summarizes the history and features of Microsoft's .NET Framework. It discusses the major releases from .NET 1.0 in 2002 through the current .NET 4.0. For each release, it highlights new capabilities like Windows Forms, ASP.NET, WPF, WCF, and LINQ. It also summarizes new areas in .NET 4.0 like parallel computing, the dynamic language runtime, and improvements to ADO.NET, Entity Framework, and Windows Workflow Foundation.
4. .NET Framework 1.0 First public beta at PDC 2000 RTM: early 2002 Introduced the world to “managed code” GC, JIT C# Coherent Framework XSP….ASP+…ASP.NET! WinForms
5. .NET Framework 1.1 RTM Early 2003 “managed code” mainstream Ships in Windows Server 2003 Rounds out features
6. .NET Framework 2.0 RTM Late 2005 ASP.NET for the Masses Application Building Blocks Parts, Authentication, Role Management, etc Visual Web Developer Client Development ClickOnce!
7. .NET Framework 3.0 RTM end of 2006 Windows Presentation Foundation Vector Graphics, Media and UI Enters the age of UX Windows Communication Foundation Unified messaging model Windows Workflow Foundation Coordinating work with durable applications
8. .NET Framework 3.5 RTM End of 2007 Linq ASP.NET AJAX WCF/WF REST Services Workflow Services Client Sync Client app services
9. .NET Framework 3.5 "SP1" RTM Mid 2008 ASP.NET Dynamic Data ADO.NET Entity Framework Data Services (Astoria) WCF AtomPubServiceDocuments Client Client Profile Performance Working set and startup time
10. .NET Framework Current "Layer Cake" .NET Framework 3.5 + SP1 Entity Framework Dynamic Data Data Services .NET Framework 3.5 Add-in Framework LINQ WF & WCF Enhancements Additional Enhancements .NET Framework 3.0 + SP1 Windows Presentation Foundation Windows Communication Foundation Windows Workflow Foundation Windows CardSpace .NET Framework 2.0 + SP1
12. Le .NET Framework WPF Win Forms DLR ASP.NET WCF And more! LINQ Base Class Libraries The CLR JIT & NGEN Garbage Collector Security Model Exception Handling Loader & Binder
14. Les Bases… Parallel Computing Data Access Runtime DLR Integration Type Equivalence In-Process SxS Task Parallel Library Parallel LINQ Entity Framework 4 Data Services 1.5
15. Web Forms 4 - Client ID 1) User Control (No ID) 2) User Control (“HeaderForm”) Control Hierarchy 3) Drop Down List (“States”) Resulting Client IDs: ctl00 ctl00_HeaderForm ctl00_HeaderForm_States
16. Web Forms 4 - Routing ASP.NET Routing Route: Product/{name} -> Product.aspx Request: Products/Bikes WebForms Page File Name: Product.aspx Route Values: Name = “Bikes” Response
18. WPF 4 Data Grid Ribbon Multi-Touch Windows 7 Enhancements
19. Managed Extensibility Framework? The Managed Extensibility Framework (MEF) is a new libraryin the .NET Framework that enables greater reuse of applications and components. Using MEF, .NET applications can make the shift from being statically compiled to dynamically composed
24. A lot of new for WF/WCF 4 XAML-only workflows are the new default Unified model between WF, WCF, and WPF Extended base activity library Simplified WF programming model Support for arguments, variables, expressions Major improvements to WCF integration Runtime and designer improvements Service discovery for WCF Hosting & management via "Dublin“
25. ADO.NET Data Services 1.5 Server Enhancements Row count Server-side paging Friendly feeds BLOB streams Client Enhancements Row Count WPF/SL data binding
28. The Parallel Computing Initiative Letting the brightest developers solve business problems, not concurrency problems. ”Concurrency for the masses”
29. Parallel Computing with .NET 4 Task Parallel Library (TPL) Parallel LINQ (PLINQ) Coordination Data Structures (CDS) System.Threading Improvements
30. Parallel LINQ Parallel LINQ (PLINQ)enables developers to easily leverage manycore with a minimal impactto existing LINQ programming model var q = from p in people where p.Name == queryInfo.Name && p.State == queryInfo.State && p.Year >= yearStart && p.Year <= yearEnd orderbyp.Year ascending select p; .AsParallel()
37. Type Equivalence Interop Assemblies translate between managed code and COM For each interface, struct, enum, delegate, and member, contains a managed equivalent with marshalling data
39. Go Away, PIA! Compilers embedthe portions of the interop assemblies that the add-ins actually use Runtime ensures the embedded definitions of these types are considered equivalent
41. .NET Framework Compatibility .NET 4.0 is a highly compatible release .NET 4.0 does not auto–roll forward You must add a configuration file with a specific switch to get 3.5 apps to run on 4.0
42. .NET Framework Compatibility Hang on… if 4.0 is compatible, why not run 3.5 apps automatically on 4.0? The BEST thing is always to prefer running on the version of the framework you built against
48. Silverlight Modern application UI framework & runtime Rapid creation of visually stunning apps METRO themed UI controls, defined in XAML XAML, C#, HTML & JavaScript 500,000 developers spanning Windows and Web Rich media support