LabVIEW 2011 compatibility mode |
LabVIEW 2012 and later |
Generated methods use the default refnum class and are not type safe. |
Generated methods use type-safe refnum classes. |
The generated method prototype lists output parameters before input parameters. |
The generated method prototype lists parameters according to their arrangement on the VI connector pane. Inputs appear first, arranged according to the order of the terminals on the connector pane from top to bottom, left to right. Outputs appear after inputs, arranged according to the order of the terminals on the connector pane from top to bottom, right to left. |
All methods generated from Vis belong to a single class specified in the .NET interop assembly class name section on the Information page of the .NET Interop Assembly Properties dialog box. |
If a VI belongs to a project library, then the .NET method generated from that VI belongs to a class with the same name as the project library. For nested project libraries, LabVIEW generates nested classes. If a VI does not belong to a project library, the .NET method generated for this VI belongs to the class specified in the .NET interop assembly class name section on the Information page of the .NET Interop Assembly Properties dialog box. |
Methods generated from Vis containing error in and error out clusters include error in and error out parameters. .NET methods do not typically accept and return errors. |
When LabVIEW generates a .NET method for a VI, LabVIEW does not export the error in and error out clusters as parameters of the new method. Instead, the new method throws a .NET exception if an error occurs while the method is executing. This exception contains the same information as the error cluster. |