Introduction

This fix is helpful if you are using WCF streaming and you got this exception while transferring huge file using data contract. If you are using streaming and the stream is transferred to or from WCF service, then you will get an exception like

Introduction

This error can happen when you use Microsoft Team Foundation Server(TFS) and if you don’t have proper binding files. This can happen if the solution is new in TFS and there are no binding files associated with it. You can easily fix this. To fix it, you have to go to

Introduction

In this article, we will see how to create a simple WCF service. Then we will see how to host this WCF service in a console application with so called self-hosting. After that we will see how to expose service metadata via MEX endpoint. After that we will see how to create a proxy for the WCF service which has net.tcp and net.pipe endpoints using visual studio 2010.

Background

This article is all about creating, hosting and adding service reference to WCF service in client application. We will start with creating a WCF service as a class library, and then we will host it in a console application. We will expose net.pipe and net.tcp endpoints for our service. In WCF, when we add service reference via visual studio, visual studio will automatically create proxy for WCF service at client side. With basic settings, we cannot add service reference to WCF service which exposes net.tcp and net.pipe endpoints via visual studio. We will make necessary changes on WCF service so that visual studio can detect service and can add service reference to our client project.

Introduction

RadPane in telerik controls can show a header. We normally use the Header property to set the header for RadPane. This works most of the time. But in some scenarios, say for example when we use nested RadPane, this kind of usage doesn’t seem to work. The header suddenly disappears. This is a know issue in telerik.

Introduction

Often we face a situation where we have defined a DataTemplate and we need to bind to a property, most often to a Command in ViewModel. To achieve this we will define the binding and will set a RelativeSource for that binding which in some cases can ends up in an error like this. BindingExpression path error: … property not found on ‘object’ … BindingExpression:Path=… DataItem=…