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

Question

Http Standalone?.vi
Not An FTP Session?.vi
DoNIsEngineersKnowThatQuestionMarksInVINamesAreConsideredIllegalByTheABAPIAndWillBreakAppBuilds?.vi
These vi names with question marks will break a build.  The ones I found were all part of the internet toolkit.  Please don't do this anymore NI.
-Devin
I got 99 problems but 8.6 ain't one.

Answer 1

Bob_H. wrote:
Billings11, thanks for bringing this issue to our attention, my apologies for misunderstanding the original post.  Travis and I went ahead and created a couple of bug reports on this issue (#120518, and 120633) to fix the internet toolkit VI names, as well as to look into a system to prevent occurrences like this from occurring again.  Thanks again for reporting this to us.
Jon D, I am interested looking into your situation in more detail.  Those file primitives (and others like "Search/Split String", "Get Date/Time String", etc...) shouldn't be actual files anywhere on the system (unless you are using the compatibility VI in the "_oldvers" llb which no longer does anything but return an error).  Could you elaborate a little bit on the problem you experience with files of these names, and perhaps attach an example?
The problem was when I was printing the documentation for the VI as an HTML file.  As part of the documentation, I would add the list of subVI's (Print->Print Contents->VI Documentation->List of SubVIs and Express VIs selected).  When the HTML files were generated, if you looked at the HTML, where the Open/Create/Replace.vi would be listed in the subVI's list, would be a broken link, because no Open/Create/Replace.png coulld be created.
I do note that when I tried to replicate this with 8.5, that the Open/Create/Replace.vi doesn't cause a problem because it appears that primitives aren't added to the list of subVI's anymore with that print option.
Jon D
Certified LabVIEW Developer.