Quote from bluematrix:
ok - saw I have two different options offered already - but which is better?
also have you actually experience doing this? are there any limitations using a dll or going through c# excel-dna? can you use objects exactly the same way etc?
ALSO - what if you have lot of code in non-CLI that might be difficult to recompile..
I've never had any difficulties recompiling native code in C++/CLI, and C++/CLI seems to link in native libraries and automatically generate the wrapper/transition code to get information out of the native libraries properly.
I use C++/CLI quite a bit, mostly because using COM libraries or various broker interfaces and changing from broker to broker on all the various prop front-ends always involves some random new hodge-podge of Windows-related technology. C++/CLI is somewhat of a god-send because it serves as a sort of glue for connecting old/native code with systems that use .NET.
The added benefit is that you can still write solid, re-usable C++, and not feel bound to .NET forever.
I can't comment on Excel-DNA; I've never used it. I was just proposing an alternative if you didn't want to be forced into C#.