04-16-2021 03:31 AM
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
04-16-2021 06:06 AM - edited 04-16-2021 06:28 AM
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.
01-22-2025 08:15 AM
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🤔)