[BUG]-Missing Minimum Essentials Version

[jonnyarndt]

Describe the bug
When loading the QSC DSP EPI (no other EPI's and no configuration file) console reports that the EPI is missing a minimum Essentials version.

[15:58:26.479]App 3:Done with .cplz archives
[15:58:26.481]App 3:Loading assemblies from loadedPlugins folder...
[15:58:26.502]App 3:Loaded assembly 'QscQsysDspPlugin', version 2.1.0.39568
Notice: SimplSharpPro[App03] # 2024-10-04 15:58:26 # App 3:Loaded assembly 'QscQsysDspPlugin', version 2.1.0.39568

[15:58:26.502]App 3:All Plugins Loaded.
[15:58:26.506]App 3:Loading Custom Plugin Types...
[15:58:26.528]App 3:MinimumEssentialsFrameworkVersion not found.  Loading plugin, but your mileage may vary.
Warning: SimplSharpPro[App03] # 2024-10-04 15:58:26 # App 3:MinimumEssentialsFrameworkVersion not found.  Loading plugin, but your mileage may vary.

Notice: SimplSharpPro[App03] # 2024-10-04 15:58:26 # App 3:Loading legacy plugin: QscQsysDspPlugin
[15:58:26.528]App 3:Loading legacy plugin: QscQsysDspPlugin

[15:58:26.534]App 3:Done Loading Custom Plugin Types.
[15:58:26.534]App 3:Folder structure verified. Loading config...

To Reproduce
Steps to reproduce the behavior:

1. Load Essentials v1.16.0.
2. Push QSC EPI into plugins folder.
3. Reload Essentials app.

Expected behavior
A minimum version used for development testing of the EPI should be captured in the EPI.

[jtalborough]

@jonnyarndt - I don’t think there is a requirement to state a min essentials version unless there is a dependency. I don’t believe there is dependency for the QSC EPI.

In either case, feel empowered to add it.