AcitveX, Automation, Programmable, Ol2e Tomatas Tomatoes, Potatats Potatoes,
lets call the whole thing off :o)

All I know is that if I don't have the Programmable key in the registry
Excel doesn't list the Components and if I do it does.

I will have a look at the ComRegisterFunctionAttribute, but was hoping to
find a simpler route. All I really want is the quickest way to develop addin
worksheet functions, mainly for my own consumption, instead of using VBA.

I certainly wouldn't be using this stuff for wide scale distribution yet, I
almost got fired for recommending COM Excel addins which, proved v. dodgy,
back in 96.

Thanks for your help.


"Rob Teixeira [MVP]" wrote in message
...
Actually, ActiveX is a bit of a marketing term for COM components that
support automation.
If all you need is the programmable key, my advice about adding a custom
registration function and tagging it with the ComRegisterFunctionAttribute
will work. Just create the key inside that function using the
Microsoft.Win32.Registry class.

-Rob Teixeira [MVP]


"Frank X" wrote in message
...
I think you are missing the point, the COM object is registered
automatically by Visual Studio as part of the build process (I think it
automatically calls regasm.exe). The COM object is registered OK and is
usable from Excel/VBA. This isn't my problem.

However I want to use the server as an Excel "Automation Add-in"
(meaning
I
don't need a VBA wrapper function), this requires the COM component to
be
an
ActiveX component, apparently a COM component only becomes an ActiveX
component if it has the registry key /CLSID/'guid'/Programmable.

It is only the /CLSID/'guid'/Programmable key that is missing and I was
hoping I could just add an attribute to my C# file to cause regasm.exe
to
create it automatically.

Please forgive me if I have misunderstood, I am relatively ignorant of
this
stuff.