There are many posts on stackoverflow regarding the System.Net.Http.Primitives assembly error related to the Google .NET API client. The standard workaround involves using App.config/Web.config's bindingRedirect to reroute to the right assembly version at runtime (example). As far as I understand, however, this is not an appropriate workaround if application developers must produce DLLs built on the Google .NET APIs (say, as a plugin for another application) because bindingRedirects will only be processed for the plugin's hosting application. There are separate discussions on fudging bindingRedirects for DLLs (example), but they're loaded with proverbial warnings of "danger: unstable ground. Tread at your own risk". Is there a recommended alternative to bindingRedirects for application developers building DLLs that leverage the Google .NET API?
Asked
Active
Viewed 529 times
1
-
Would you mind clarifying your issue a little bit more, its not something I have seen before. Or you could post it here so that we can look into your issue https://github.com/google/google-api-dotnet-client/issues. I need a way to recreate it if you can reproduces it that would be great. – Linda Lawton - DaImTo Jun 25 '15 at 06:46
-
Thanks very much, DalmTo. I've tried to clarify the issue in a new Issue Ticket: https://github.com/google/google-api-dotnet-client/issues/555 . Thanks again! – aklein Jun 25 '15 at 19:59
-
I will check it out in the morning thanks for reporting it – Linda Lawton - DaImTo Jun 25 '15 at 20:08