Can I ActiveX control a software developed on .net framework from LabWindows/CVI

[Rajev]

Hello,

I have a software that has been developed in .net framework, and has many features exposed for automating through ActiveX controls.I would like to know, if I can ActiveX control that software that has been developed on the .Net framework, from LabWindows/CVI.

Thanks in advance,
Rajev

[bilalD]

Hello Rajev

If you can use the software from any ActiveX enabled language (VB, VC++), it means all the correct COM interfaces have been exposed and this would mean that you can use the CVI ActiveX controller wizard to create a C wrapper for it. Once you run the wizard, you can use the functions generated by it to controls the software with its ActiveX interface.

CVI offers this capability to allow you to talk to any kind of activex control or server.

Hope this helps

Bilal Durrani
NI

[Rajev]

Hello bilaID,

Thanks for the response!

As of now, I am not sure, if the software is capable of being controlled from other languages like VB, VC++.

I will give some more background on the Issue that I have at Hand!

Initially, I had a software 'abc', that exposed Activex objects, which I could control from LabWindows/CVI.Now, the same software, is being enhanced, and they are coding it in .net framework.

Now my question is, Can I Still ActiveX control it from LabWindows/CVI? Will there be any Issues as the software 'abc' is now developed in .net framework?

I might be able to ActiveX control 'abc' from VB .net or so!! Are there any specific updates given by NI for LabWindows/CVI to ActiveX control .net applications?

Thanks again,
Rajev.

[bilalD]

If the newer version of the software is being developed using .NET, its up to the developers to expose functionality via activex. It's not something that will happen automatically since .NET is a completely different framework. So you will have to refer to the software's documentation whether they will expose this kind of functionality for this software. If they explicitly mention that you can still use the newer version from VB 6.0, VC 6.0 ( or any other non .NET compiler ), it probably means they're wanting to preserve backwards compatibility. If they expose functionality via activex, it wont matter whether the control was written in .NET. You'll be able to use it as if it was the same control you were using previously. Which means that you will
still be able to program it as you were doing previously with CVI without needing anything extra from CVI.

Currently CVI does not provide any tools for talking to .NET components directly.

I hope this explains things.

Bilal Durrani
NI