Differences between .Net framework 3.0,3.5,4.0 and 4.5 .

This article discusses the features introduced in Microsoft .Net Framework 2.0, 3.0, 3.5, 4.0 and the newly introduced 4.5 framework.

A image diagram of representing the components included over the .NET framework 2.0.

• New features included in .NET framework 2.0

1. - ADO.NET 2.0
2. - SQL Server data provider (SqlClient)
3. - XML
4. - .NET Remoting
5. - ASP.NET 2.0

• New features included in .NET framework 3.0 

1. - Windows Communication Foundation(WCF)
2. - Windows Presentation Foundation(WPF)
3. - Windows Workflow Foundation(WF)
4. - Windows CardSpace(WC)

which takes a large impact on development sector

• New features included in .NET framework 3.5 

1. - This framework expand support for distributed mobile applications by including the Windows Communication Foundation (WCF) technology
2. - Adds new language features such as LINQ
3. - Introducing new APIs based on community feedback
4. - Improves debugging with updated diagnostic tools and features.
5. - Improved support for the development of AJAX-enabled Web sites
6. - ASP.NET and Visual Web Developer now support the creation of both ASMX and WCF-based Web services

• New features included in .NET framework 4.0 

1. - The .NET Framework 4 is highly compatible with applications that are built with earlier .NET Framework versions
2. - This framework support Portable Class Library, which will compatible for windows Apps and desktop development and web development projects
3. - It updates property values, improvements in string handling, and other improvements. 
4. - The new System.Diagnostics.Contracts namespace contains classes that provide a language-neutral way to express coding assumptions 
5. - The dynamic language runtime (DLR) is a new runtime environment that adds a set of services for dynamic languages to the CLR. 

In this above post I explained the basic differences among .NET Frameworks. I hpe you enjoyed it so please send your feedback and queries. Thnak You.

Is overloading possible in WCF? If yes then how?

     Yes, by using [OperationContract(Name="OverloadedName")] But, still outer world will get them with unique and different name. Overloading is a technique to write manageable/maintainable code. But in case of WCF service, uniqueness is required for generating WSDL, and that can be done either by using unique method name or unique OperationContract's name attribute value. Interfaces plays an important role and provides much flexibility for this. We can write many implementations of an interface, and it gives more flexibility plus concise. So why to think on overloading for WCF service methods?

    

    Example  :-

                 
   [OperationContract(Name="AddInt")]

       public int Add(int a, int b)

       {

          return a+b;

          }

      

   [OperationContract(Name="AddDouble")]

       public double Add(double a, double b)

       {

          return a+b;

          }

      Note:- here we have overlaoded the methods but these are still unique by name for outer world.

     In the above post I explained how overloading can be done in WCF. I hope you enjoyed this post so please comment your feedback and queries. Thanks You.