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 de to OperationContracts definere det samme antal og de samme typer af parametre. I dette tilfælde er nogle af argumenterne forskellige. Du kan løse det ved at sørge for, at OperationContracts definerer det samme antal og typer af argumenter i den samme rækkefølge. 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, the two OperationContracts must define the same number and types of parameters. In this case, some of the arguments are different. To fix it, ensure that the OperationContracts define the same number and types of arguments, in the same order. Alternatively, changing the name of one of the methods will prevent matching.

Search by Google