Is this possible? I have a .bundle plugin which is held centrally and copied to users local drive and loads on start up. I use the xcopy shell command in the acaddoc.lsp to copy contents of folder including updates to local drives. Obviously there will be a sharing violation if plugin is trying to be updated on autocad start up. Therefore, can a plugin be disabled, updated and restarted when autocad is started somehow? Any guidance much appreciated. Cheers, Robbo.
That entirely depends on the nature of the value of the ModuleName XmlAttribute being loaded within your ComponentEntry XmlNodes.
FWIW - The issue you're experiencing is not uncommon for those attempting to utilize Autoloader in-house, you can only push updates for components that are not read-only, regardless of when you 'push'.
At session start, the Autoloader mechanism creates the necessary registry entries, modifies SFSP, and even loads compiled assemblies (.DLL cannot be unloaded) prior to any Acad* file being loaded in the startup sequence... LISP ComponentEntries are still loaded after AcadDoc.lsp though. For the former, you need a mechanism in place that evaluates if newer components exist, and if able to reload does so (such as ARX, CUIx, etc.). If not, prompt for session restart, or user log off/on if relying on NETLOGON, etc. to 'push'.
There are many ways to notify user of an update, that can be included in your original app, such as bubble, notification center, alert (God forbid a thousand times!),
TaskDialog, etc... Choose the one you feel is best, and something you can work with easily.
Regretfully, Autoloader does not play nicely with non-local components to-date (something I've requested of Autodesk for years)... You'll have to roll your own.
The one silver lining, is that Autodesk is determined to support, and enhance Autoloader, particularly given its self-inflicted dependence to it for delivery of [3rd party] Exchange Apps... This as demonstrated with the new Autoloader features for 2015+ mentioned
here.
Cheers