Exclude help files from build output

[Konan__]

I have noticed that if the source VIs have a CHM files specified in the VI property -> Documentation -> Help file, 

that file is output when you build the executable with Application Builder.

How can I avoid that? I see no option for that in application builder.

Most drivers CHM are useless in the output folder.

thanks

[wiebe@CARYA]

One way would be to delete the chm files in a post build action, added to the build script...

EDIT: Alternatively, you can try to remove the help dependency in a pre build action.

[Mads]

Dooes anyone have a nice solution to this already implemented?

If the help files are removed after building the application the installer will not build...Even if you delete the chm and html files in a post-action of the application build the installer build will fail as it uses the build preview as its reference.

The help file references have to be removed, preferably just for the build really, they are nice enough to have in the development environment...and in my case there are often so many VIs with such references it should be done programmatically...

(An exclude help files option in the application build might be an idea for the idea exchange🤔)

[fmorandat]

The chm file comes from this vi property : 

(<=> Documentation in the vi property)

-> You can imagine a pre-build action checking all the vis of your application.

But basically, renaming the original chm files on the hard-drive is enough : the dynamic build preview process does not find them. So the installer builder will work.

Could be done also in the pre&post action.

The last point is : if the chm files are located in a restricted access directory, like Program Files, you will have to do it manually or with a dedicated separated program with higher privileges.

[Andrey_Dmitriev]

---

@fmorandat wrote:

The chm file comes from this vi

---

This issue is being tracked as Bug 2870271, seems to be fixed at least in 2026 Q1:

In the past I have seen lot of IMAQVision.chm in my builds, but now its clear.

[fmorandat]

2026 ? Great ! I’ve been working on this since this morning (PPL context). 😄

Well, we're stuck with 2025 for the time being.

[Andrey_Dmitriev]

---

@fmorandat wrote:

2026 ? Great ! I’ve been working on this since this morning (PPL context). 😄

Well, we're stuck with 2025 for the time being.

---

No, in PPL Context you will still get it in 2026 as well:

because "LabVIEW R&D decided that including the CHM file dependency in PPL builds is correct behavior because PPLs are sometimes used to distribute VIs that are used for development."

[Mads]

So, does LabVIEW 2026 skip all chm files (apart from those associated with PPLs as has been pointed out here now), or just the ones that used to be included with IMAQVision etc?

Ideally there should be an option in the build process here that covered PPLs as well (inlude chm or not). A less ideal but tolerable solution would be for the installer builder to at least accept it if chm files have been removed from the application build...

[Andrey_Dmitriev]

---

@Mads wrote:

So, does LabVIEW 2026 skip all chm files (apart from those associated with PPLs as has been pointed out here now), or just the ones that used to be included with IMAQVision etc?

---

Hard to say... Previously, I saw not only IMAQ Vision but also DAQmx files, but now they are all gone (but only when built into an application).

[fmorandat]

I tried to rename the file. In LV2025 the preview doesn't find it, so no chm with the ppl. (Daqmx only, didn't try for Vision)