Nothing explicit in the documentation's I saw but given that you have the following on each machine you should be able to deploy via a single pyxll.xll and pyxll.cfg (can be named whatever but just needs a xll and cfg combo with the same base name):- Python interpereter installed- Correct PyXLL version for local interpreter installed- Python DLL exposed to system path- Python standard modules available in PYTHONPATH Will test via VM later when I have time to confirm.

QuoteOriginally posted by: HansiNothing explicit in the documentation's I saw but given that you have the following on each machine you should be able to deploy via a single pyxll.xll and pyxll.cfg (can be named whatever but just needs a xll and cfg combo with the same base name):- Python interpereter installed- Correct PyXLL version for local interpreter installed- Python DLL exposed to system path- Python standard modules available in PYTHONPATH Will test via VM later when I have time to confirm.I think you need also to deploy the compiled pyc files? The .xll is not recompiled.

Not sure, but given that the function definitions are added to the xl_func decorator wouldn't that mean the xll needs to be recompiled to accurately expose update information/function defs?

QuoteOriginally posted by: HansiNot sure, but given that the function definitions are added to the xl_func decorator wouldn't that mean the xll needs to be recompiled to accurately expose update information/function defs?Good point, I don't know how it works. But for sure the .xll is not recompiled.

No recompilation should be necessary as Excel add-ins register themselves the functions they want to expose rather than these functions being loaded from the "dll" in some standard way. This means that new add-in functions can be defined at run-time and in the case of Python integration addins these newly defined functions can point to new Python functions also defined at run-time. If you want to see how this works I have the source code to something similar at http://www.bnikolic.co.uk/expy/expy-source.html

QuoteOriginally posted by: bojanNo recompilation should be necessary as Excel add-ins register themselves the functions they want to expose rather than these functions being loaded from the "dll" in some standard way. This means that new add-in functions can be defined at run-time and in the case of Python integration addins these newly defined functions can point to new Python functions also defined at run-time. If you want to see how this works I have the source code to something similar at http://www.bnikolic.co.uk/expy/expy-source.htmlHey, thanks. Interesting indeed.