Right now I have a set of tools for AutoCAD that get deployed to users in our company. Currently they are being deployed via an msi that I maintain through a Visual Studio Setup Project. The files include .NET dlls for some of our custom commands and lisp functions as well as many script, lisp, .pc3, .ctb, etc. files. The current method for installation is as such:
At log in time it checks if the machine has the tools installed or needs an update. If they are not installed then it silently runs the msi. If they are installed but need an update then it does an uninstall then install also silently.
When the user closes out of AutoCAD it also runs this same method except that it notifies the user via the system tray not to reopen AutoCAD until the update is complete.
Right now it appears that either the log in or the updater isn’t always working because I have users getting errors caused by missing components and they seem to occur randomly. I’m assuming that one of the msis is getting cutoff mid process.
Taking into account that I need to be able to do updates on the fly (i.e. tell the user to exit AutoCAD and get back in to receive the updates) what are some alternative methods to update my AutoCAD plug-in?
We place our .Net dll’s in a shared network folder. When the users launch AutoCad, we run a LISP routine that performs a ‘netload’ of the dll’s. This way, if we want to update, we just rename the old dll’s and place the new ones in the shared network location. The next time users launch AutoCad, they will have the latest. You stated that you want to update on the fly and let the users know, which is something that we don’t have to worry much about. If we are concerned, we’ll just send an email to our AutoCad user group and tell them they must restart for the latest changes to take affect.
This probably isn’t exactly what you’re looking for, but hopefully it made you aware of a possible ‘different’ approach.