Den opgavebaserede, asynkrone OperationContract-metode '<var>Method name</var>' i typen '<var>Type Name</var>' stemte overens med de asynkrone OperationContract-metoder '<var>X</var>' og '<var>Y</var>', fordi de har det samme handlingsnavn '<var>Z</var>'. Når en synkron OperationContract-metode sammenkædes med et par asynkrone OperationContract-metoder, skal de to OperationContracts definere den samme returtype. I dette tilfælde er returtyperne forskellige. Du kan løse dette ved at sørge for, at metoden '<var>Method name</var>' og metoden '<var>Y</var>' har den samme returtype. Alternativt kan du ændre navnet på en af metoderne for at undgå sammenkædningen.

The task-based asynchronous OperationContract method '<var>Method name</var>' in type '<var>Type Name</var>' was matched with the asynchronous OperationContract methods '<var>X</var>' and '<var>Y</var>' because they have the same operation name '<var>Z</var>'. When a synchronous OperationContract method is matched to a pair of asynchronous OperationContract methods, the two OperationContracts must define the same return type. In this case, the return types are different. To fix it, ensure that method '<var>Method name</var>' and method '<var>Y</var>' have the same return type. Alternatively, changing the name of one of the methods will prevent matching.

Search by Google