Den synkrone OperationContract-metoden <var>Method name</var> i typen <var>Type Name</var> ble tilpasset den oppgavebaserte asynkrone OperationContract-metoden <var>X</var> fordi de har samme operasjonsnavn X. Når en synkron OperationContract-metode tilpasses en oppgavebasert asynkron OperationContract-metode, må de to OperationContract-metodene definere samme antall og typer parametere. I dette tilfellet er noen av argumentene forskjellige. Dette løser du ved å sikre at OperationContract-elementene definerer samme antall og typer argumenter i samme rekkefølge. Du kan også endre navnet på en av metodene for å hindre at de samsvarer.

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