Licensed component not playing well with DI design

Question

We've licensed some third-party e-mail components and have developed a set of components for our system that uses them. These components are then loaded dynamically at runtime by an IoC container.

However we have recently noticed in testing on a non-development machine that because the main .EXE which is "hosting" our components does not reference nor include a .licx for the third-party e-mail components (separation of concerns and all that) that it is causing the license check of the third-party e-mail components to fail.

Is there anyway around this?

It seems to be a pretty big flaw in the whole LicenseManager, .licx etc story of .NET?

Thanks!

Answer 1

License files are just like configuration files - you can make libraries which reference them, but ultimately there is an artifact which has to live on disk with the executable.

I assume you have a .licx file and just don't want to reference it in any way from the application project. You can avoid that by including the .licx file in the installer - it ends up on disk in the right place and the application project is none the wiser.