Torben
An XLA is pretty much just a hidden workbook with VBA code. You can't
create these in C#. You can do COM addins and automation addins (for UDFs)
in .net.
What about Visual studio 2005 tools for office, does it offer a good
replacment for a xla?
Maybe something that I can put on a server so nothing has to be installed on
any PC?
Only request is that the user can access the code using a function call
inside excel
Torben
Whether a VBA xla addin or a vb6.0 Com addin or a .net com or automation
addin or an XLL toally depends on what you are doing.
If you are server side and you want to avoid Excel on the server (and you
should) then a standard COM component or a .net assembly will prob be best.
you can call these from a VBA wrapper by setting a reference. Or as you say
use a VSTO solution - these are available in VS 2003 and the beta 2005 ones
are supported now for deployment.
The choice depends on how much use of Excel/.net you need, how much future
proofing you need, if all clients have xl2003 etc etc.
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.