Difference between WCF and ASP.NET Web Service

.Net rovides various options for creating services under .NET Framework. Before WCF, ASP.NET Web Services are used to ceate service in .NET Framework. Now WCF is the latest programming model for building and developing service-oriented application. WCF allows applications to communicate with each other in distributed environment. WCF is a set of technologies that covers ASMX web services, Web Services Enhancements (WSE), .NET Remoting and MSMQ. In this article, you will learn the differences between ASP.NET Web Service and WCF.

WCF

ASP.NET Web Service

ServiceContract and OperationContract attributes are used for defining WCF service.

WebService and WebMethod attributes are used for defining web service.

Supports various protocols like HTTP, HTTPS, TCP, Named Pipes and MSMQ.

Supports only HTTP, HTTPS protocols.

Hosted in IIS, WAS (Windows Activation Service), Self-hosting, Windows Service.

Hosted only in IIS.

Supports security, reliable messaging, transaction and AJAX and REST supports.

Support security but is less secure as compared to WCF.

Supports DataContract serializer by using System.Runtime.Serialization.

Supports XML serializer by using System.Xml.Serialization.

Supports One-Way, Request-Response and Duplex service operations.

Supports One-Way and Request-Response service operations.

WCF are faster than Web Services.

Web Services are slower than WCF

Hash Table can be serialized.

Hash Table cannot be serialized. It can serializes only those collections which implement IEnumerable and ICollection.

Unhandled Exceptions does not return to the client as SOAP faults. WCF supports better exception handling by using FaultContract.

Unhandled Exceptions returns to the client as SOAP faults.

Supports XML, MTOM, Binary message encoding.

Supports XML and MTOM (Message Transmission Optimization Mechanism) message encoding.

Supports multi-threading by using ServiceBehaviour class.

Doesn’t support multi-threading.

Comments

Accessing File Stored in Windows Azure Blob Storage Using jQuery

Did you know it was possible to access the Windows Azure Blob Storage directly from JavaScript, for example using jQuery? At first, it sounds obvious, since Blobs are after all accessible from a public UR. But in practice, there is a very big hurdle: the Web browser’s Same Origine Policy or SOP, that restricts JavaScript code to accessing resources originating from the same site the script was loaded from. This means that you will never be able to load a Windows Azure Blob using XMLHttpRequest for example! Fortunately, there is a popular workaround called JSONP (“JSON with Padding”). The idea behind this technique is that the script tag is not submitted to the SOP: an HTML page can thus load a JavaScript file from any site. So, if you expose your data in an “executable” form in JavaScript, a page will be able to load this data using a script tag. For example: <script type=”text/javascript” src=”http://www.sandeepknarware.in/exemple.jsonp”> </script> But how can ...

gcAllowVeryLargeObjects Element

There are numerous new features coming with .NET 4.5 and here, on this blog, you can find several posts about it. But the feature we are goint to talk about today is very exciting, because we were waiting for it more than 10 years. Since .NET 1.0 the memory limit of .NET object is 2GB. This means you cannot for example create array which contains elements with more than 2GB in total. If try to create such array, you will get the OutOfMemoryException. Let’s see an example how to produce OutOfMemoryException. Before that Open Visual Studio 2012, and create C# Console Application, like picture below. First lets create simple struct with two double members like example below: 1 2 3 4 5 6 7 8 9 10 11 12 public struct ComplexNumber { public double Re; public double Im; public ComplexNumber( double re, double im) { ...

Support for debugging lambda expressions with Visual Studio 2015

Anyone who uses LINQ (or lambdas in general) and the debugger will quickly discover the dreaded message “Expression cannot contain lambda expressions”. Lack of lambda support has been a limitation of the Visual Studio Debugger ever since Lambdas were added to C# and Visual Basic. With visual studio 2015 Microsoft has added support for debugging lambda expressions. Let’s first look at an example, and then I’ll walk you through current limitations. Example To try this yourself, create a new C# Console app with this code: using System.Diagnostics; using System.Linq; class Program { static void Main() { float[] values = Enumerable.Range(0, 100).Select(i => (float)i / 10).ToArray(); Debugger.Break(); } } Then compile, start debugging, and add “values.Where(v => (int)v == 3).ToArray()” in the Watch window. You’ll be happy to see the same as what the screenshot above shows you. I am using Visual Studio 2015 Preview and it has some limitati...

Dot Net Deewane

Search This Blog