Hi,
after successful export of our "big and complex" LVOOP application to .NET interop assembly (DLL), everything seems fine except that we can't instantiate the main application class by calling the default constructor in C# something like:
MainClass main = new MainClass();
This call will compile but will trigger a LabVIEW file browse dialog asking for mydllname.dll/MainClass.lvclass .
I found this forum entry from 2014, which describes the same error and reports it solved by LabVIEW 2013 SP1 f1. Still, we experience the very same problem with LabVIEW 2014 (no service pack). Is it possible that LV 2013 SP1 f1 was released *after* LV 2014? I don't think so.
The description of the corresponding ticket (CAR 447058) says "Under certain conditions, LabVIEW cannot create a functional .NET interop assembly if the assembly contains LabVIEW Class." Whatever those conditions are, we cannot reproduce the error on a toy example but cannot get rid of it in our production code.
Unfortunately, we cannot easily try it with a later LabVIEW version due to IT issues in a big company.
Fortunately though the workaround mentioned in the original thread (wrapping the instantiation of the class) seems to work for our specific example.
Any help is appreciated,
Peter
