Though WCF claims the multiple end point connectivity in the next gen distributed computing, itz an interesting problem in terms of client connectivity reference.
Letz talk with a specific example. A console client application is created to consume a WCF Service. With the usual process of VS2008 WCF example, every thing works fine. Cool! One thing got noticed is the directory structure. In the sense, WCF Service Reference is mandated to be at Service References folder of the client application. On relocating to another directory structure, the app couldn't locate the service at all. Itz weird. Drilled little bit. Noticed VS Data Source file for the service reference namely 'ConsoleApplication1.WCFServiceRef. CompoisiteType', as refered in the image. The content of the data source says
Version=0.0.0.0, Culture=neutral, PublicKeyToken=null
It talks about type info with reference of 'Reference.cs' file. No where in the content and directory, the absolute path is not specified. Still, app needs 'ServiceReference' under the client application folder. Quite thrill to know!