error 1055 calling .net constructor in runtime environment

[Lila K]

I have a VI that calls a .net assembly, and it works perfectly on my development machine - the VI is in the same directory as the dll. 

This VI gets deployed on a production machine, with runtime only, in two ways, and both result in an error 1055 because the .net constructor reference is invalid.

The first way is I am building an executable.  When I run this executable on my development machine though, it's fine.  I've looked in the directory structure for the executable, and the dll exists in the data directory.

The second way I am deploying is through TestStand and the deployment utility.  When this VI is run through TestStand, I get the error.  After using the deployment utility, I can see in the directory structure that the dll and the VI are in the same directory.

Any ideas what has gone wrong?  I'm not that familiar with integrating .net and labview. 

[Nadim R]

Hi,


One workaround regarding error 1055 is to place the .Net portion of the code inside a non-reentrant subVI.  To have a non-reentrant SubVI, go to File>>VI Properties>> Execution and uncheck "reentrant execution".  I hope this helps.


Regards,

Nadim
Applications Engineering
National Instruments

[Lila K]

Actually, the .net portion of the code is already inside a non-reentrant subVI.  Problem code and small project are attached.  When the exe built by this project is run on my production machine, I get there error.  To run you don't need to fill in any of the fields - just hit 'GO' on the top level VI.

Is there some other dependancy or path that i may have to set up on my development machine?  So far is has run time 8.2 and .net 1.1 framework.

[Nadim R]

Hi,

I ran your VI as well as your executable here inhouse and both seem to be working fine without the error.  I followed your instructions and left all fields on the front panel blank.  To test your application, I left all fields blank and ran the top level vi and then i ran I build the executable and ran the exe.  Am I missing some steps to reproduce the error?


Regards,

Nadim
Applications Engineering
National Instruments

[Lila K]

No, running the exe that I included, with all fields blank, is all I have to do to reproduce the error on my production machine.  This is leading me to believe that there is a configuration problem with the production machine.  This machine has LabVIEW 8.2 runtime, and then I installed .NET framework 1.1.  Is there anything else I might have to do?  Should I have installed them in a different order, or do I need any additional packages?

[shb]

Hello Lila K,

Have you solved your problem? I have the same one. (It is described in this thread, message #3) . Do you have any hints?

Greetings,
shb