When VIs are built into an application, revision numbers and history are wiped. What you can do is to store the revision number elsewhere before the build. For example, you could write an utility that reads the revision number of one or each VI in the applicaion and store it in the "VI Description" string or as the default value of a front panel control. You run this utility before building the application. That way, the revision number is available in the application.
Now I see what he meant. I never build an application with the default menus and never saw the VI properties under File. I've always found the VI revision number pretty worthless anyway since a single VI might change numerous times between one release and the next of an executable. For built applications, I put a revision level string in an "About" VI and a splash screen.