LabVIEW as an in-process COM-server

[rberger]

Hello:

At the moment, I evaluating if LabVIEW is the best tool suitable for my next task.

I would like to know if LabVIEW is an in-process COM server—an ActiveX DLL—that implements the IDTExtensibility2 interface. I am trying to add a COM add-in for a current Microsoft product.

The MS notes also states the following:

Non-modal forms cannot be displayed directly from a COM add-in. If you have non-modal forms, you can have your add-in call an external program (such as a Visual Basic executable) that enables a connection.

Does LabVIEW meet these criteria or do I have to program in VB?-((

Robert

[rolfk]

rberger wrote:

> I would like to know if LabVIEW is an in-process COM server—an
> ActiveX DLL—that implements the IDTExtensibility2 interface. I
> am trying to add a COM add-in for a current Microsoft product.

LabVIEW is not an in-process COM server. LabVIEW is started as a
separate process either as development system or as runtime executable
and the Active X interface is out of process to the other application
invoking LabVIEW's Active X interface.

LabVIEW is also not embeddable into other applications through Active X.

Rolf Kalbermatter