Publish FlexLib into it's own NuGet package

n8wrl

From a question I asked elsewhere…

https://community.flexradio.com/discussion/8033913/dlls-since-4-2-20

I would like to see if we can get community support for Flex to publish its DLL's into a NuGet package we developers could then grab and build into our code. The solution at present (which I haven't gotten to work yet) is to download the source and build the DLL's ourselves. I would really like to treat this as a black box and include it in my projects like I used to when they were shipped with SmartSDR.

Thank you all, and 73!

-Brian n8wrl

Trucker

Thanks for pointing this out. It shows how long it's been since I updated my projects. I have a feeling that another reason that they are combining the dll's is that they are using 3rd party, licensed dll's and they cannot make them available to developers who haven't purchased them from the original owner. In the past I tried to link to one of the 3rd party dll's and Visual Studio popped up a message saying that I needed a license from the company that created it in order to use it. A couple of them were custom controls for things like the slide out menus. If we have to compile FlexLib from source it might help to know what lines of code can be safely commented out to build the dll's. That, and what order they should be built in. This was one of the reasons I just copied the dll's from the SmartSDR install folder to a sub-folder in my project. It was a lot less headache instead of building them in the correct order so the next build would have the previous dll available for linking and proper reference.

James

WD5GWY

n8wrl

James, That's exactly how I got the DLL's before 4.2.20.

it depends on what your projects are doing. As far as I can tell, there are no references to licensed libraries in the API source we can download and compile, although there are references to obsolete and at least one potentially compromised library. The source code buids. Since "final linking" doesn't happen until runtime, I'm failing on one of possibly several external references that must have been baked into the DLL's back when they shipped them.

To support this developer-ecosystem it would be cleanest and most welcome for Flex to go the Nuget route!

73

-Brian n8wrl