At the hedge fund where I recently worked we deployed VSTO add-ins using ClickOnce.
That was no problem at all for users. We simply sent them a link to the deployment server and had them create a desktop shortcut for the ".application" file. (I liked that better than "setup.exe".)
I don't see any reason why that would not work equally well for NetOffice.
BTW: You can include any number of additional support assemblies in the "required files" on the ClickOnce property page.
If you prefer to avoid learning the details of ClickOnce, you can always try out something like Squirrel.Windows, which might arguably be simpler in many cases.
That was no problem at all for users. We simply sent them a link to the deployment server and had them create a desktop shortcut for the ".application" file. (I liked that better than "setup.exe".)
I don't see any reason why that would not work equally well for NetOffice.
BTW: You can include any number of additional support assemblies in the "required files" on the ClickOnce property page.
If you prefer to avoid learning the details of ClickOnce, you can always try out something like Squirrel.Windows, which might arguably be simpler in many cases.