Laurent Kempé

I saw your comment at timeheuer's blog.

I thought the reason is something different.

My Project's assembly name and namespace dose not contains any dot, but that symtom is still exist.

In my case it seemed to depend on project namespace and main form having the same name: "TestHarness".

In that case Reference.cs contained "TestHarness.TestHarness.WCFCommunicatorServiceReference" (leading to build errors) and after renaming the form to "TestHarnessMain" it changed to "TestHarness.WCFCommunicatorServiceReference".

HTH

It worked for me when I renamed main form name different than name space. Just like what GDL suggested

In my case, I have got DataContract classes created twice.

public partial class XXXX : object, System.Runtime.Serialization.IExtensibleDataObject, System.ComponentModel.INotifyPropertyChanged {}

public partial class XXXX : object, System.ComponentModel.INotifyPropertyChanged {}

This error disaapears when i remove FaultContract from service interface. Any help

I had the same problem with the dublicate classes/properties and RaisePropertyChanged method after I had added a lot of code to the service.

On this blog (it.toolbox.com/.../wcf-svcutil-proxy-generation-issues-25084) I found a hint: "For some reason, if SvcUtil can't find one of the types referenced in the services, it generates proxies for all types even if the defining assembly has been referenced correctly."

I had forgotten to add "[DataContract]" to one of the classes used by the service methods. After I added it the problem was gone.