Currently, the AVEVA Adapter Configuration Utility is a single program that handles all AVEVA Adapters. Over time, as more AVEVA Adapters get introduced and the amount of adapter-specific features and accommodations increases, the AVEVA Adapter Configuration Utility will grow, possibly to a point that using it on low-resource computers becomes infeasible. Rather than shut down ideas that are meant to improve the AVEVA Adapter Configuration Utility just to preserve its small file size, consider introducing separate installers/files for the adapter-specific features.
This would be similar to the ICU Control programs that come with PI Interfaces, which give the PI Interface Configuration Utility functionality specific to that PI Interface. The difference with the equivalent programs/files for AVEVA Adapters would be that they would not be part of the AVEVA Adapter install kit, partly because AVEVA Adapters have bare installers rather than install kits, and partly because packaging both together would negate some of the "lightweightness" of the AVEVA Adapters. That is, those who plan to use AVEVA Adapters without the AVEVA Adapter Configuration Utility should not be forced to install or even download a program/file that is needed only when the AVEVA Adapter Configuration Utility is being used.
I am not even necessarily suggesting that these programs/files be made. The suggestion is for these programs/files to be made if the alternative, at some point in the future, is to sacrifice the quality of the AVEVA Adapter Configuration Utility just to keep it as a small, single program with only its current dependencies.
The "/files" part of this suggestion is to account for the fact that the AVEVA Adapter Configuration Utility does not need to follow exactly in the footsteps of the PI Interface Configuration Utility. The adapter-specific stuff does not need to be its own program. It could even be in a separate file, placed in a designated folder that the AVEVA Adapter Configuration Utility reads.
