Bug #5182
openBetter install experience for plugins with additional dependencies
0%
Description
Right now, If my plugin DLL needs further 3rd party DLLs to operate (or even initialize), I'd have to copy them manually to the AdiIRC Plugins directory before hand.
This experience could be improved. Suggestions:
1) Some kind of reflection of inspection of the DLL to find the referenced assemblies and copy them if they are in the same place as the plugin DLL.
2) Some kind of extra metadata in the plugin interface or some external (optional?) file to describe dependencies.
3) Some kind of a dedicated archive extension - Like .APA (AdiIRC Plugin Archive) or .APZ (AdiIRC Plugin Zip, if we're specific) where all the required dependencies are in this archive to begin with. In this case, Maybe the plugin should be in its own directory as well to prevent conflicts with other plugins (i.e. 2 versions of Newtonsoft.Json, for example) - Though this might be an issue/suggestion on its own.
No data to display