So everyone is going to be connected to the same addin on the
network? I can see how that could cause problems because of sharing
violations and also the chance that one user could muck up the code
somehow and that code would trickle down to all the users of the
addin. I simply create an install package when deploying addins. I
use InnoSetup to create the install package. I use a separate
worksheet for installation of the addin which is executed once the
install is complete. The code used in the Open event of this workbook
is something like below. The addin is then installed without the user
having to interact in any way, other than to click Enable Macros if
necessary.
Private Sub Workbook_Open()
Dim wBook As Workbook
On Error Resume Next
Set wBook = Workbooks("addin_name.xla")
start:
'close book if open
If Not wBook Is Nothing Then _
Workbooks("addin_name.xla").Close
'uninstall if installed
If AddIns("addin_name").Installed = True Then _
AddIns("addin_name").Installed = False
'install add-in
AddIns.Add FileName:="C:\addin_name", _
CopyFile:=True
AddIns("addin_name").Installed = True
Set wBook=Nothing
ThisWorkbook.Close False
End Sub

Exton wrote:
Hello,

I've written my first Excel Add In and am delivering it to a customer site
tomorrow. Initially I planned to have each user copy the Add In to their own
computer but now I'm wondering if I should deliver the Add In to a location
on their LAN and have users install it by browsing to the LAN location from
the Add In manager. This latter approach would seem to make re-deployment of
subsequent versions much easier.

Is the LAN based approach for an Excel Add In typical? Any downsides that I
should consider?

thank you.