NI: Please don't put illegal vi names in your toolkits, thanks

[billings11]

I would suggest that NI put in place a test pre-release where they build all vi's in vi.lib including all toolkits into a source distribution using the ABAPI.  The distribution will error on any vi's with illegal filenames.  Most of the bugs and errors I've seen with the last several labview releases have to do with problems building exe's or source distributions, or inconsistency in the behavior of the application builder from version to version.  Usually source code bugs are easy to work around, but bugs that only happen when you build an exe or source distribution are far more aggrivating and tedious to find solutions.  I would recommend NI put extra emphasis on testing all code in executable form, as well as ensure all new labview structures work properly in exe form as well as in development mode.  That will also easily identify the type of error in this thread.

Thanks.

[rolfk]

Would selecting the Application Builder option to actually build an executable in the old way where all VIs are stored inside an LLB in the executable (except duplicate names, such as LVOOP VIs which get in their own external directories) help workaround this problem?

Message Edited by rolfk on 03-20-2010 05:53 PM