Note that there are some explanatory texts on larger screens.

plurals
  1. POUnable to invoke Bing Translator service on WP
    primarykey
    data
    text
    <p>After the migration, gone are the good old days when Microsoft provides a handful of functions on Bing Translation. And new account keys are only valid to the new service root:</p> <pre><code>https://api.datamarket.azure.com/Data.ashx/Bing/MicrosoftTranslator/v1 </code></pre> <p>instead of something like:</p> <pre><code>http://api.microsofttranslator.com/V1/SOAP.svc </code></pre> <p>or:</p> <pre><code>http://api.microsofttranslator.com/V1/SOAP.svc </code></pre> <p>And that's not the end. When I try to add service reference to it, the VS just says:</p> <pre><code>EntityType 'Microsoft.Translation' has no key defined. Define the key for this EntityType. </code></pre> <p>Or throws some exception on permission.</p> <p>Before that, I tried to use the Helper Class that ships with the subscription. It took me long to modify the code for use on WP8 - regarding some issues on System.Data.Services.Client (some incompatibility caused by WCF 5 on the client?) and asynchronous calls. The result was:</p> <pre><code>System.InvalidOperationException:There is a type mismatch between the client and the service. Type 'Microsoft.Translation' is not an entity type, but the type in the response payload represents an entity type. Please ensure that types defined on the client match the data model of the service, or update the service reference on the client. </code></pre> <p>I checked the response and found nothing wrong:</p> <pre><code>After the migration, gone are the good old days when Microsoft provides a handful of functions on Bing Translation. And new account keys are only valid to the new service root: https://api.datamarket.azure.com/Data.ashx/Bing/MicrosoftTranslator/v1 </code></pre> <p>instead of something like:</p> <pre><code>http://api.microsofttranslator.com/V1/SOAP.svc </code></pre> <p>or:</p> <pre><code>http://api.microsofttranslator.com/V1/SOAP.svc </code></pre> <p>And that's not the end. When I try to add service reference to it, the VS just says:</p> <pre><code>EntityType 'Microsoft.Translation' has no key defined. Define the key for this EntityType. </code></pre> <p>Or throws some exception on permission.</p> <p>Before that, I tried to use the Helper Class that ships with the subscription. It took me long to modify the code for use on WP8 - regarding some issues on System.Data.Services.Client (some incompatibility caused by WCF 5 on the client?) and asynchronous calls. The result was:</p> <pre><code>System.InvalidOperationException:There is a type mismatch between the client and the service. Type 'Microsoft.Translation' is not an entity type, but the type in the response payload represents an entity type. Please ensure that types defined on the client match the data model of the service, or update the service reference on the client. </code></pre> <p>I checked the response and found nothing wrong:</p> <p> Microsoft Translator https://api.datamarket.azure.com/Data.ashx/Bing/MicrosoftTranslator/v1/Translate?Text='hello'&amp;To='nl' 2012-11-22T23:20:10Z https://api.datamarket.azure.com/Data.ashx/Bing/MicrosoftTranslator/v1/Translate?Text='hello'&amp;To='nl'&amp;$skip=0&amp;$top=1 Translation 2012-11-22T23:20:10Z Hallo (Sorry but the xml doesn't display properly.)</p> <p>I even tried to use the traditional method for accessing OData, but all in vain. A little mad honestly...</p> <p>I've googled enough but still couldn't find a solution to the new Bing Translator interface. Does anyone have similar problems with mine? Thanks in advance.</p> <p>I even tried to use the traditional method for accessing OData, but all in vain. A little mad honestly...</p> <p>I've googled enough but still couldn't find a solution to the new Bing Translator interface. Does anyone have similar problems with mine? Thanks in advance.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload