Message in Norwegian (Bokmal) (Norsk (Bokmål))

Den oppgavebaserte asynkrone OperationContract-metoden <var>Method name</var> i typen <var>Type Name</var> ble tilpasset de asynkrone OperationContract-metodene <var>X</var> og <var>Y</var> fordi de har samme operasjonsnavn <var>Z</var>. Når en synkron OperationContract-metode tilpasses et par asynkrone OperationContract-metoder, må de to OperationContract-metodene definere samme returtype. I dette tilfellet er returtypene forskjellige. Dette løser du ved å sikre at metoden <var>Method name</var> og metoden <var>Y</var> får samme returtype. Du kan også endre navnet på en av metodene for å hindre at de samsvarer.

Unlocalized message

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
Available localized messages
Korean (한국어) Polish (Polski) Portuguese (Brazil) (Português (Brasil)) Russian (Русский) Spanish (Español) Swedish (Svenska) Turkish (Türkçe) Chinese (Simplified) (中文(简体)) Prior (Message) Chinese (Traditional) (中文(繁體)) Arabic (العربية) Czech (Čeština) Danish (Dansk) Dutch (Nederlands) Finnish (suomi) French (Français) Next (Message) German (Deutsch) Italian (Italiano) Japanese (日本語) Hungarian (magyar) Hebrew (עברית) Greek (Ελληνικά)