How to hide the dependecies of a dll from the code calling it?

by DefenestrationDay   Last Updated January 13, 2018 10:05 AM

I have a class library that calls dll_A.
dll_A has dependencies on WPF.

How to I wrap or isolate my class library so that the code calling my library does not need to have a dependency on WPF?

(My class library obviously has to depend on WPF, but the only output is Byte[]).

In other words, I want my library to act as an entirely different process, as a sort of 'buffer', and the calling code does not care about how it works, only that it outputs Byte[].

I don't even know what this technique is called..

Related Questions

When should I create separate function (or class)

Updated September 01, 2017 19:05 PM

Engineering approach for Metadata Driven Architecture

Updated September 11, 2017 18:05 PM

Managing linked resources in UI

Updated July 08, 2017 04:05 AM