Closed zell12 closed 5 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.
Is there already a PR for this? Or is it necessary at all?
Thanks @apoblock for the suggestion. I tried that fix: didn't heal the problem. Interestingly works fine when run in VS, just not standalone.
Fixed in 2.1.0 by copying system.net.http.dll.
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.![image](https://user-images.githubusercontent.com/15136766/42804877-d6126c82-89dc-11e8-816a-e10f53b7d795.png)