Invalid contract attribute for IMetadataExchange

Question

I have upgraded a WCF Service to .NET Framework 4.5. After doing so I noticed a blue squiggly line around the IMetaDataExchange in the host config file.

<

Answer 1

Perhaps not the answer for the OP, but others with this problem should check that [ServiceContract] is declared for the interface of your services, because this produces the exact error.

Answer 2

I found the problem to be that the contract attribute is case sensitive.

I had a different solution that referenced the same service, but did not have any warnings in the app.config. i ran compare in notepad++ on the system.serviceModel section of the app.config and it highlighted the difference in case between the two contract attributes.

as soon as i modified the contract attribute to the correct case sensitive spelling the warning went away instantly

Answer 3

I had the same problem on client side. For me the solution was to delete and add the service reference again.

Answer 4

Can you delete .SUO (solution Users Option file) file after closing VS? This will reset the cache for XMLEditor component in VS and will fix your problem.

Answer 5

I had a similar problem to this - several name and contract attributes showing in the App.Config of my WCF Service with the dreaded blue squiggly, and warnings showing up in the Error List.

In my case the problem was that after creating the services and contracts I had refactored the namespaces of the service project, so the generated solution-specific *.xsd was using the new namespaces but my refactoring tool hadn't updated the App.Config with the changes. Going in and adding the fully-specified namespaces fixed the issue.

Answer 6

Closing VS2013 Prof, removing the "obj" folder and recompiling has done the job for me.