« Introducing ExcelDna - DotNet for Applications | Main | Some new examples »

Comments

M.Grieser

I have a question...

Once I created the Test1.xll and the Test1.dna (which worked just fine), what exactly needs to be distributed with the Excel Workbook for users to access the .xll functions?

Govert

You need to give the users Test1.xll and Test1.dna. However, they must also have the .Net 2.0 runtime installed, have the macro security relaxed and maybe fix the version loading issue described above. But the only ExcelDna bit that you need is the .xll file, to which you add your .dna and any .dlls you create.

R. Sarkissian

Can you create an object in the C++ code, and expose its properties and methods in Excel?

R. Sarkissian

govert

Currently objects can not be exposed to Excel directly from managed code, only static methods. Of course you can wrap your object methods by creating corresponding static methods, as you would when creating an .xll in C/C++. I plan to add some built-in object support to be compatible with the Excel Services UdfClass/UdfMethod declarations. Properly doing object references and object tracking for user-defined classes might come later.

N. Teofilov

Greet stuff! Wow!
Thank you!

I have two questions:

1. How to create a menu with c#?

2. How to add description to the Add-In from c#?

Andrew Roberts

Can I add the XLL to my existing c# project and call the Excel functions from some c++ code?

Regards

jake.

Any plans to support separate AppDomain with private .config file - without this deployment becomes problematic.

Thanks.

jake.

btw i forget to mention that i have developed software using ExcelDna and i believe is a quality product. it just needs a few touches on the deployment side before i can really leverage it in a production environment. support for object handles would also be awesome.

Javier Medina

Would a sample of code to use a dll created with VB code be possible? I'm too neophite to get it on my own!

govert

Hi Javier,
To make a .dll out of your VB.NET code, use vbc.exe in the command line. You might need to translate some of the command line arguments - just check the help for vbc.
You are welcome to send me e-mail if you still have problems.
Regards, Govert

The comments to this entry are closed.