Proper generic interfacing of FlexLib by logging program

I am prototyping an integration of the FlexLib to a logging program. I can connect to the radio and slices fine, but have a generic design question. 

I dislike coupling. So, I created a new Classlibrary called "FlexConnector" which will do all the interfacing to the multiple FlexLib libraries. The reason why I try to not reference the FlexLib from the main application is that it will pollute the code and logic. Assume that Flex is not the only radio type, so many other radios need to be interfaced.

Now, many data from FlexLib properties need to be read by the main program. For example, what frequency a slice is on. I see multiple options:

1. Add references to the FlexLib and WFPUIFramework to the Main application. Then the FlexConnector dll can pass around the Slice object, and read and set anything by directly accessign the FlexLib properties. 

2. Have FlexConnector DLL expose a bridge object for the Slice, so the FlexLib and WPF libs are not needed to be known by the main application. In this case many properties and functions have to be adapted. 

3. Same as 2, but instead of creating an object, use a Dictionary. The dictionary is owned by the FlexConnector but exposed for reading to the main applicaiton. Main application needs to know the formatting of the keys (coupling). Also, only strings or simple types can be put in the dictionary values, or the FlexLib will have to referenced as well. 

4. ?

In general, I estimate that about 20% of all properties will be needed by the main logger. 
I favor a solution where the FlexConnector class library can be shared with other programs, so a loosely coupled solution would be desirable. 

How have others solved the problem?  Any suggestions are welcome.

73
Andy
KU7T