News for hackers. Stuff that matters.
Re:Applying programming language research ideas to transform... by cm2187 on Sunday January 20, 2019 @01:28PM (#18954606)
Possibly stating the obvious, but you know that you can manipulate the excel object model from ExcelDNA in the same way that you can with VBA (thanks to VSTO!).

Add a reference to Microsoft.Office.Interop.Excel, and get a handle on the Excel Application object using ExcelDna.Integration.ExcelDnaUtil.Application.

Alternatively you can use the excellent NetOffice.Excel (instead of Office.Interop.Excel), which will have less functionalities but with better version support.

Re:Applying programming language research ideas to transform... by keithalewis on Sunday January 20, 2019 @02:15PM (#18954938)
If you know C++ and want to embed C++ objects in Excel you can use a library I wrote. Here is an example of how single inheritance works: https://github.com/keithalewis/xll12/blob/master/sample/hand...
Re:Applying programming language research ideas to transform... by clausok on Sunday January 20, 2019 @01:59PM (#18954822)
Where has NetOffice.Excel been hiding?! Thank you for that.

What I've found with interop is there's a little more debuggability/edit-and-continue friction that can accumulate into a large loss of time during development. Maybe that loss is offset, or more than offset, by doing the interop with a vastly superior language. I'm not sure. Any thoughts about this trade-off?

Re:Applying programming language research ideas to transform... by cm2187 on Sunday January 20, 2019 @02:14PM (#18954935)
I don't know. I find VBA to lack so many modern features (type inference, linq, generics, etc) that I favor using a more modern language over edit&continue. VBA and interop have nearly the same syntax so you can always toy in VBA and then implement it in .net. NetOffice sometimes has a different syntax so is a bit more iterative.