Hi Raj,
You can try out this repository.
govert/TestComServer18 (github.com)
It uses the dSPACE COM tools (dspace-group/dscom: dscom, a toolkit for creating and registering type libraries (tlb) and additional interop helper methods for COM (github.com)) to make the .tlb file.
One difference from the real tlbexp is that it does not support AutoDual interfaces.
-Govert
--
You received this message because you are subscribed to the Google Groups "Excel-DNA" group.
To unsubscribe from this group and stop receiving emails from it, send an email to exceldna+u...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/exceldna/4f366d97-4ce6-4575-996e-ab9c7164abefn%40googlegroups.com.
Do you mean you’ve lost IntelliSense in the VBA, or for the UDFs when entering formulas in the sheet?
-Govert
--
You received this message because you are subscribed to the Google Groups "Excel-DNA" group.
To unsubscribe from this group and stop receiving emails from it, send an email to exceldna+u...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/exceldna/89c3694c-6fd8-419a-b836-ff3e5ab996a7n%40googlegroups.com.
Hi Raj,
Does it work right with the sample project when running on your machine?
If so, but your own project is still problematic, then you might need to make sure the various COM Guids are changed.
I think sometimes VBA cached type library information, and if you update your types VBA does not pick it up.
-Govert
From: exce...@googlegroups.com <exce...@googlegroups.com> On Behalf Of Chintu
Sent: 12 November 2024 22:46
To: Excel-DNA <exce...@googlegroups.com>
Subject: Re: [ExcelDna] Excel DNA with .NET 8
Hi Govert,
I am trying to replicate your methodology in the sample project you sent in my own code and I am getting a 'Class not registered' error in VBA when I try to initialise the managed object. I am pretty sure I am doing exactly what you are doing. Not been able to find the issue yet. Any suggestions?
Many thanks
Raj
On Friday, November 1, 2024 at 1:43:50 PM UTC Govert van Drimmelen wrote:
Hi Raj,
Once you have dsCOM working right to make a type library, your IntelliSense in VBA will work as before if you define the right interfaces in the code.
Just removing the "ClassInterface.AutoDual" will mean you only have dispatch interfaces (that's because ClassInterface.AutoDispatch is the default).
So you have to define an interface explicitly and then set that as the ComDefaultInterface.
Then you get VBA IntelliSense - see the sample project I sent the link to earlier
-Govert
To view this discussion visit https://groups.google.com/d/msgid/exceldna/a19c887e-8835-44f8-82a0-dd6e6a98a6ffn%40googlegroups.com.