DotNet constructor node in LabVIEW 2013

[f2bstaffan]

I am talking to a WLAN tester Agilent N4010. Access is done through DotNet. This has been working fine in previous LV versions, but in LV2013 I can not access the constructors. The attached picture shows LV2012 to the left and LV2013 to the right.

I have tried to save a vi in LV2012 (with the constructor selected) and then open it in LV2013. The VI is broken and I can not open the dialog "Select Constructor...".

Anyone having similar isues?

/Staffan

[Norbert_B]

Staffan,

do other .NET assemblies work fine?

If some do, some not, is it the version of the .NET framework which causes the fails?

If there is no specific pattern or all assemblies fail, you might want to try a repair install of LV.

Also double check with a different PC please.

Norbert

[f2bstaffan]

Some works, some don't. Some can not use the same Assembly-version, like Micrsoft.VisualBasic.

How do you know which version to install?

/Staffan

[Norbert_B]

Staffan,

the .NET assembly should contain information about the framework version it is using (e.g. 3.5, 4.0, ...).

Do those which work share a specific version which is different to those which do not work?

Norbert

[f2bstaffan]

I think version 1.1 is requried. I have this version in my C:\Windows\Microsoft.NET\Framework folder but not in my C:\Windows\Microsoft.NET\Framework64 folder.

Thanks for your help!

/Staffan

[Norbert_B]

Staffan,

i am still trying to fiddle things out, but that might a problem.

Previous versions of LV (e.g. 2012) were using the CLR 2.0 as default interface to .NET assemblies.

Please remark that the CLR version number does not always "match" the .NET framework version number, see more details on Microsoft here.

As you can see, there was a shift between CLR 2.0 to CLR 4.0 in .NET framework 4.0. NI did update the .NET interface in LV 2013 to use CLR 4.0 by default.

So, this CLR version is not able to execute your assembly anymore (but .NET framework 3.5 could as the used CLR was still 2.0!).

Microsoft states that previous assemblies should execute correctly in newer CLR versions, but obviously there is a mess-up in the exposure of the function prototypes.

Important question:

Is it possible for you to get an updated version of the assembly which requires CLR 4.0 (or later)?

Norbert

[f2bstaffan]

I have contacted Agilent for a possible solution.

/Staffan