just a perspective ...

..  and attach a distinct and  meaningful name. When publishing metadata for a service that exposes two different service contracts in which each contain an operation of the same name an exception is thrown.  For example, if you have a service that exposes a service contract called ICarService that has an operation Get(Car c) and the same service exposes a service contract called IBookService that has an operation Get(Book b) , an exception is thrown or an error message is displayed when generating the service's metadata.  To remedy this issue you may want to consider one of the following approach: Rename one of the operations. I'd suggest give them some meaningful name, any way (such as GetCar(Car car) and GetBook(Book book) ) Set the operation Name to a different name Set one of the operations' Namespaces to a different namespace using the Namespace property Reference :  Metadata Architecture Overview

2013 is the year with distinct numbers (digits) since 1987.. and 1987 was the year when I was out of high-school into the exciting world of pursuing higher education at universities. 1987-1990 : B.S. (Statistics) 1990-1993 : M.S. (Computers) a great snapshot of the MSU at evening time

During the holiday break, the last couple of weeks, I read up a book that resonates so well with my personal observations about the transformation happening in Modern India, these days. This blog, being about a perspective, I couldn't not mention about it. A very brilliantly written and a must read for people interested in understanding various transformation a life juxtaposes while the country is going through some serious, drastic changes - cultures which have flourished over not years, but centuries ... amazon.com URL for the book