Den synkrone OperationContract-metode '<var>Method name</var>' i typen '<var>Type Name</var>' blev sammenkædet med den opgavebaserede, asynkrone OperationContract-metode '<var>X</var>', fordi de har det samme handlingsnavn 'X'. Når en synkron OperationContract-metode sammenkædes med en opgavebaseret, asynkron OperationContract-metode, skal de to OperationContracts definere det samme antal og 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 synchronous OperationContract method '<var>Method name</var>' in type '<var>Type Name</var>' was matched with the task-based asynchronous OperationContract method '<var>X</var>' because they have the same operation name 'X'. When a synchronous OperationContract method is matched to a task-based asynchronous OperationContract method, 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