Getting credentials are invalid on CLI but not on desktop client

MicrosoftTranslator / DocumentTranslator-Legacy

Microsoft Document Translator (Archive) - Replaced by the MicrosoftTranslator/DocumentTranslation project in this repository.

Other

409 stars 152 forks source link

Getting credentials are invalid on CLI but not on desktop client #65

Closed zell12 closed 5 years ago

zell12 commented 6 years ago

I'm trying to use the translator via command line but I'm receiving 'Credentials are invalid' error when using the same apikey that I used on the desktop client that's working.

Note, I also tried using the apikey I've managed to get to work in the past, but now it's not working as well.

apoblock commented 6 years ago

The issue happens because TranslationServices.Core is using different version of System.Net.Http - version 4.3.3 should be referenced with the Nuget package, rather than 4.1.1.2 from the framework.

zell12 commented 6 years ago

Is there already a PR for this? Or is it necessary at all?

chriswendt1 commented 6 years ago

Thanks @apoblock for the suggestion. I tried that fix: didn't heal the problem. Interestingly works fine when run in VS, just not standalone.

chriswendt1 commented 5 years ago

Fixed in 2.1.0 by copying system.net.http.dll.