We are using the 3rd party application "Diadem" from "National Instruments", which provides it's own dialog engine. On these "dialogs", we can use visual ActiveX-Controls, that we browse within the dialog editor.
To add to the list of useable controls, we have wrapped an existing .Net-control into a COM wrapper, to mimic an ActiveX.
That works fine as long as we are registering the new control with admin rights.
But to distribute it with our projects, we have to register it without admin rights.
And here the "fun" begins: using RegAsm with /regfile produces a .reg-File with i have patched so that it uses HKCU instead of HKLM. With this file it was possible to register the new control.
Using createobject for one of the registered classes returned an object that is not NULL. Without further tests i would say it is registered quite ok.
But the dialog editor does not see it. Probably it is only looking into the HKLM tree.
Are there any ideas on how i register a .Net-ActiveX-Dll without admin rights and still enable my 3rd party program to browse it like any other ActiveX-Ocx?
Thanks in advance,
Ruediger
What I have tried:
I've tried the idea from
vba - Registering .Net COM DLLs without Admin rights / regasm - Stack Overflow[
^]