App Builder breaks VIs

[ScotchTape]

Every time I try to build my LabVIEW project, which by the way works fine within LabVIEW, into a stand alone application I an error like this...

"An error occurred while building the following file:

C:\DPS\Digital MacroView\Version 2\Alignment Station\Application\AlignmentStation.llb\CalculateOffset.vi

The VI became broken during the build process. Open the Build Specification and enable debugging to include the front panel and block diagrams."

The funny thing is the error switches between different files, niether of which appears to have anything wrong with them (see attached JPEG).  I've already set the "Additional Exclusions" option to "Do not disconnect type definitions or remove unreferenced members".

Does anyone know how I can troubleshoot this error?  The information provided by the error message isn't very helpful.  Is there more detailed information somewhere?

Thanks

[Doug M]

ScotchTape,

This error has been seen only a couple of times and it would be helpful if you could post the project that is reproducing this error.  If you don't want to post your code publicly you can also open a service request through our support channels.

The one reference I could find to this dealt with needing to have the front panel of the main top level VI open when the project is built, and with having polymorphic VIs replaced.

[ScotchTape]

Doug,

Here is a simplified version of my application that still exhibits the problem...

Thanks,

David

[Doug M]

David,

I am able to reproduce the error but unfortunately I don't have a work around.  This is essentially the same error as has been reported to R&D as issue #467EDOVQ, however I'd like to ask R&D for any additional information they may have on a workaround.  I'll let you know if I find out anything else.

Message Edited by Doug M on 03-16-2007 05:48 PM

[ScotchTape]

Thanks!  I appreciate your efforts in trying to get to the bottom of this issue.

David

[Doug M]

Hi David,

So I did some further testing to try to pinpoint what is causing this error and it seems that using any .NET constructor, .NET method, or .NET property node within a LV Object Oriented class VI will cause this error upon building the application.  This was reported to R&D (#47KGBBG0) for further investigation. 

One thing that does seem to work as a (not very elegant) workaround is to wrap .NET contructor, method, or property nodes in a subVI that is NOT part of an OOP class.  This subVI, even when used by a OOP VI, seems to allow the application to build.

Hope the info helps, even if it wasn't the answer you were looking for...

[ScotchTape]

Doug,

I appreciate the follow up email.  I'm sure I can use the work around if needed.  Thanks.

A couple of quick questions...

1)    Do you think this is something R&D can resolve in the next month or so, and if so will there be a software patch available?

2)    Do you know if the LabVIEW Database Connectivity Toolkit would exhibit the same kind of behavior if I use it within my LabVIEW class?

Thanks again!

David

[Doug M]

Hi David,

For question 1, I would doubt a patch would be issued in that timeframe,

for question 2, the Database Connectivity Toolkit will not have this problem since it does not use .NET, plus all of the functionality is within a subVI.

Hope this helps!

[AnalogKid2DigitalMan]

Can Scotch Tape be used to fix the broken vi's?

Sorry, couldn't resist. I have nothing else to offer on theis topic.

Good Luck.

[ScotchTape]

I think it's gonna take duct tape.