Resolution on "Could not load file or assembly 'System.Net.Http.Primitives'" error for .NET DLLs?

551 Views Asked by At

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?

0

There are 0 best solutions below