Haven't had any experience in writing ActiveX controls in C# - it was bad enough writing them in VB6
Just a couple of thoughts though. First, have you come across this Microsoft sample that may be of some assistance? Secondly, I would generally opt for control registration via a command line option using regsvr32, so I'm not sure if maybe the problem is in your RegisterClass method of the control object - perhaps a required registry entry to properly register the control has been overlooked.
as you can see in my attachment => i already create the acticex control but for some reason it doesn't work in Processbook, but in the ActiveX control test container it works.
i also added
in the procbook.exe.config file which is normal the reason it doesn work for an Addin in processbook, but it doesn't help
in tstcon it works
3 of 3 people found this helpful
as long as I know there is no support from OSIsoft for .NET ActiveX. You will have to use C++ or VB6.
Here is a thread from some years ago. Give a look at answer from Laurie Dieffenbach in the following thread:
Unfortunately the PLI referred (PLI 4027OSI8) is not public so that I do not know if it has been addressed in the meanwhile.
Good call Nicola - reading the response from Laurie, I do now recall that issue, and as far as I remember it never was addressed to provide PB support. If custom ActiveX controls really are needed, then VB6 or C++ will be the options to use. Alternatively, this sounds like a good candidate for a custom PI Coresight symbol.
Inserting .NET control directly within a pdi file will not work as PLI 4027OSI8 stands.
However it is possible to contain the control within a docking Window/Toolbar/Addins.
1 of 1 people found this helpful
.NET controls are not the same as ActiveX controls created in .NET.
Native .NET controls have never been supported directly within a PDI, and this PLI refers to support for ActiveX controls created in .NET. The referenced content for .NET add-ins to PB is useful for hosting native .NET controls (not ActiveX controls) within dockable windows, but the original post specifically referred to ActiveX controls being used directly on the display surface. Controls written in VB6 or C++ are still the only options for custom ActiveX components being used directly in a PDI on the display itself.