Issues with creating EXE in LV 9 (w/ patch)

[jonathanupr]

When creating an executable in LV 9 (with the new patch installed), it is taking around 7 to 8 minutes to create the executable... where as in LV 8.5 it only took around 1 minute (same VI no changes).

After the EXE is done I go into my build folder and find the following folders:  NI_HTML, NI_report, NI_Standard Report (these all containing actual VIs (not executables) from the above folder llbs.   This never occurred in 8.5 nor in 7...what's going on here?  I've got a few customers waiting on the EXE and am just stalled due to this.

[Anil_Reddy]

u mean installer? or EXE?

[jonathanupr]

I am referring to the building of the .exe (main vi) ... the step prior to building the installer, that is after I create the "exe." vi ... I insert the "exe." into the installer "Source Files".

[jonathanupr]

Why is the Application builder (when creating an exe.) wanting to load all of these LLBs?

This just makes a damn mess of things.

LabVIEW 9 thus far just sucks!  Just wasting my time.

It may be my ignorance here, but why make things harder!!!

[smercurio_fc]

This is due to the Report Generation VIs having been re-written in LabVIEW 8.6 to be based on classes. Please see here.

[jonathanupr]

This is a joke right?  "cleaner method of distribution"? 

So I have to do more work to upgrade NI's lower level LLBs in LV 9 when in the 1st place I paid NI to upgrade from 8.5 to 9... doesn't seem close to an upgrade (in regards to plug & play quality) to me!  The resource page that supposedly shows you how to fix this issue is vague!  ???????   Geesh.

Maybe this is a better way to do things with the "Object Oriented Program" & Classes... though, for a someone only a few years deep in LV...this is not efficient at all (NI is going to start killing it's marketable value if they make this any more difficult).

"Solution:
The Report Generation Toolkit 1.1.3 released with LabVIEW 8.6 was rewritten using LabVIEW classes and LabVIEW Object Oriented Program. Because of these changes and the improvements in performance, there are some files that currently are added explicity to the build directory. Therefore, the behavior is expected and the executable will run without problems. In a pursuit of a cleaner method of distribution when configuring the Build Specifications for executable, all the generated folders can be placed into one support directory."

[jonathanupr]

Okay, so do I just add these to my project like the jpg. shows?

What else do I need to do?

This a 1st time using LV Classes directly.

Message Edited by jonathanupr on 03-09-2010 11:44 PM

[gmart]

The behavior you are seeing was a general issue with building applications that used LV classes. It became more pronounced when the Report Generation Toolkit was modified to use LV classes. In LabVIEW 2009, built applications were changed to alleviate this issue. In the build specification properties dialog, there is now an option on the Advanced page named "Use 8.x file layout". For compatibility reasons, this option is checked for all projects created before LabVIEW 2009. This option controls whether internal to the build application, the layout of the files are stored either flat (pre 2009 behavior) or with hierarchy. So, if you uncheck the option and rebuild, you should not get any files outside of the built application.

The knowledge base that was linked was a workaround for pre-LabVIEW 2009. It is still valid even with 2009 but is not necessary.

[jonathanupr]

Yeah,

unchecking "use 8.x file layout" doesn't solve the problem.

Anyone with any kind of helpful info on how to solve these issues would be appreciated.

[gmart]

I would make sure the destination directory is empty before rebuilding after the checkbox is unchecked. App builder does not "clean" the destination directory so if you rebuilt, any existing directories would still be present. When you say "doesn't solve the problem", do you mean that the directories are still present or that the app doesn't work?