Dot Net Framework 2.0 Vs Framework 3.0 Vs Framework 3.5

Microsoft .NET Frameworks .NET Framework 2.0 .NET Framework 3.0 .NET Framework 3.5

Microsoft .NET Framework 2.0

Microsoft .NET Framework 2.0 The first two .Net frameworks (1.1 & 2.0) focused on allowing many

different languages to communicate with a common set of libraries translated through the Common Language Runtime (CLR). Introduced with .NET 1.1 and enhanced with .NET 2.0, the CLR works on a relatively simple concept: A common runtime model executes code for any system running the .NET Framework. What this means to you as a developer is that you don’t need to keep relearning languages for different technologies. For instance, a C# developer who writes Windows Forms applications take the knowledge used for building forms and apply it to writing web pages. Similarly, a Visual Basic .NET developer can switch from writing mobile applications to writing web services. The CLR acts as an arbitrator and communicates back and forth. It brings a lot of evolution in class of the framework and re-factor control including the support of  Generics  Anonymous methods  Partial class  Nullable type  .NET Micro Framework

Microsoft .NET Framework 3.0

Microsoft .NET Framework 3.0 It is also called WinFX, includes a new set of managed code APIs that are an integral part of Windows Vista and Windows Server 2008 operating systems and provides

The .NET 3.0 Framework is not improving upon existing technologies but rather introducing four new foundation technologies: Windows Communication Foundation (WCF), formerly called Indigo; a service-oriented messaging system which allows programs to interoperate locally or remotely similar to web services.  Windows Presentation Foundation (WPF), formerly called Avalon; a new user interface subsystem and API based on XML and vector graphics, which uses 3D computer graphics hardware and Direct3D technologies.  Windows Workflow Foundation (WWF) allows for building of task automation and integrated transactions using workflows.  Windows CardSpace (WCS), formerly called InfoCard; a software component which securely stores a person's digital identities and provides a unified interface for choosing the identity for a particular transaction, such as logging in to a website. 

Microsoft .NET Framework 3.5

Microsoft .NET Framework 3.5 The .NET 3.5 Framework is not improving existing technologies &

introducing technologies. It implement Linq evolution in language. So we have the following evolution in class: Linq

for SQL, XML, Dataset, Object Addin system p2p base class Active directory ASP.NET Ajax Anonymous types with static type inference Paging support for ADO.NET ADO.NET synchronization API to synchronize local caches and server side datastores Asynchronous network I/O API Support for HTTP pipelining and syndication feeds. New System.CodeDom namespace. .NET 3.5 has good Designer experience, JavaScript debugging and IntelliSense features, and the ability to view and even step into the core .NET Framework code during debugging.