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 opgavebaseret, asynkron OperationContract-metode sammenkædes med et par asynkrone OperationContract-metoder, skal eventuelle yderligere attributter erklæres i den opgavebaserede, asynkrone OperationContract-metode. I dette tilfælde indeholder den asynkrone OperationContract-metode '<var>X</var>' en eller flere attributter af typen 'X'. Du kan løse dette ved at fjerne 'X'-attributterne fra metoden '<var>X</var>'. 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 task-based asynchronous OperationContract method is matched to a pair of asynchronous OperationContract methods, any additional attributes must be declared on the task-based asynchronous OperationContract method. In this case, the asynchronous OperationContract method '<var>X</var>' has one or more attributes of type 'X'. To fix it, remove the 'X' attribute or attributes from method '<var>X</var>'. Alternatively, changing the name of one of the methods will prevent matching.

Search by Google