Measurement Studio for .NET Languages

cancel
Showing results for 
Search instead for 
Did you mean: 

.NET Container

 

Hi!

I have a problem with .NET Container exactly with inserting .NET Control to Container. Some control I can put into Container but mostly I get message: This assembly contains no public controls. I use LabView 8.6. I have no idea where can be the problem, but I have just started working with .NET under LabView :/.
0 Kudos
Message 1 of 7
(5,627 Views)

This simply means that none of the classes in that assembly derive from the Control base class (i.e. they don't contain any usable controls). For example, if you select the System.Windows.Forms assembly in the Select .NET Control dialog, you will notice a variety of controls availalbe (i.e. BindingNavigator, Button, CheckBox, etc). If you use some reflection tool, you can see that at some point, these classes derive from the base Control class. Then if you switch the assembly to something like System.Core, you will notice that there is a message that states This assembly contains no public controls. None of the classes in this assembly derive from the Control class.

 

Best Regards,

Jonathan N.
National Instruments
0 Kudos
Message 2 of 7
(5,624 Views)
So, I'm I good understand. I can't use .NET Container because classes don't consist on objects, which have controles?
0 Kudos
Message 3 of 7
(5,588 Views)

 

Hello!   

I have anoughter question. I select .NET Container and then browse Controle. Unfortunately sometimes I get something looks like grey small area, and sometimes I get real controle. Do anybody know where is the problem? Also when I'm trying to import .NET Controles to Palett I get this grey something. i don't have this kind of problem with ActvieX. Please help.

0 Kudos
Message 4 of 7
(5,578 Views)

Hi behemot,

 

The only thing I can think of is that the .NET control has design-time support meaning that if you were to drop this control onto a Windows Form, it would bring up some design-time wizard. LabVIEW doesn't have design-time support for the .NET container. We do have design-time support for ActiveX controls.  Is the control you are adding a native .NET control (i.e. one that would be default appear in the Toolbox inside of Visual Studio designer) or is it some control made by a 3rd party company? 

 

Best Regards,

Jonathan N.
National Instruments
0 Kudos
Message 5 of 7
(5,559 Views)

 

Controles are made by the 3rd party company. If I have a control written under ActiveX it is impossible to insert this controle using .NET Container (?) so when I try to insert the same control using .NET Container and ActiveX Container it is only possible with ActiveX Container, so probably files support ActiveX. On the other hand Constructor Node (from .NET toolkit ) supports every files. So maybe my problem is that I'm trying to put ActiveX Object in .NET Container, but I'm not sure. 

I would like to know something more about "design - time" could you explain me this in detail? 
0 Kudos
Message 6 of 7
(5,556 Views)

Hi behemot_,

 

You cannot insert an ActiveX control into the .NET container and you can't insert a .NET control into an ActiveX container. The .NET container can only except .NET controls so if you are mixing and matching, you will run into problems. We should be giving you an error if you try to insert an ActiveX control into the .NET container.

 

With regards to design-time support, you would run into issues if when you dropped the .NET control onto a Windows Form, it brought up some wizard or dialog allowing you to customize the control. This wizard would be display in LabVIEW.

 

Best Regards,

Jonathan N.
National Instruments
0 Kudos
Message 7 of 7
(5,552 Views)