.NET build Assembly usage within LV developement system (Crash)

[nottilie]

Hi all

I have created a simple VI in labview which adds two numbers.

Then I have build a "normal" dll and tested it within the LV developement system.

The next step was to build an .NET assembly and use it within the LV developement system.

I have seen this in LV2009 that it crashes the developement enviornment. 

NI sayd they will fix it for 2010.

So my question is.

Am I to stupid within 2010 to run my own build .NET assembly .

Or is it not fixed.

Is there enyone out there who knows this in detail.

Thank you in advance.

Best regards

Gernot

[smercurio_fc]

Please post your code (i.e., your project and associated VIs) rather than asking such a vague question that nobody can answer.

You are, presumably, referring to this earlier message you posted. By posting your code someone with 2010 can try it. Of course, you could just try it yourself by downloading 2010, as it comes with a 30-day trial.

[nottilie]

OK

I just build this VI in 2010 

Then I build a .NET assembly with the following prototype settings.

Finally I build the following vi which uses the .NET assemby build before.

Like this.

When I run this vi in the developement system it crashes (keeps the vi running endless)

I see this behaviour also in LV2010 so I was wondering.

If I build an application from the final VI it works perfectly.

Also if I use the assembly within VS.NET it works.

So is there still a problem in the developement system or is there a simple trick to avoid this "crash" in the developement system.

Hope now it is more clear.

Best regards

Gernot

[UM · Accepted solution]

Hi Gernot,

Unfortunately, this is a “Known Issue” in LabVIEW 2010 and it is already reported, so our Research & Development Department is already involved.

164604  - Calling LabVIEW built .NET Interop Assembly from same version of LabVIEW causes a hang.

If you build a .NET Interop Assembly and try to call it in the same version of LabVIEW, it will hang at the constructor node.
Workaround: Create the .NET Interop Assembly in a different version of LabVIEW.

LabVIEW 2010 Known Issues
http://zone.ni.com/devzone/cda/tut/p/id/11869

Regards
Ulrich
AE NI-CER