I can clear up several issues.
First, LV does not require vis to have a specific file extension. Here are some example file names that could represent a vi:
Untitled
Untitled.vi
Untitled.coolest thing ever
Untitled.vi.vi.vi.vi.txt
I like cupcakes
I _really_ like cupcakes._really_
foo.vit
foo.ctl
foo.ctt
...
VIs are marked internally to be recognizable as a vi. When you add files to a project, we actually check the file to see whether it represents a vi file type or not.
Newer things like libraries, xcontrols, lv classes, etc. have defined file extensions whose type can be determined from the extension alone.
So, if foo._vi_ exists on disk and is really a vi, it will be treated as a vi in the project.
if foo._vi_ is some other type of binary or text format (or isn't found on disk), then it will be treated as a generic 'document' in the project - just like a .txt file.
Second, clearly lv should not crash just because it encounters a file that is really a vi with an extension of ._vi_ that claims to belong to a library that either can't be found or doesn't reciprocate the claim. Anytime LV crashes, it is a bug in lv - LV should never crash. I have a CAR assigned to me to fix this specific problem.
Unfortunately, I have been unable to reproduce the crash despite many attempts. Any further help you can provide about how I might reproduce this would be greatly appreciated. Can you send me the specific ._vi_ file that crashes? From the screen shot, it appears to start with 'Agilent...' Is that the missing .lvlib? Do you know why it is still in dependencies? The only other contents of the project appear to be 'SA Output Power Managerment.lvlib'. Is the file that has the ._vi_. extension under that .lvlib somehow? To where did you add the directory - underneath the 'SA....lvlib' library?
If you can get it to crash like this again, click 'debug' and see if you can get a callstack in whatever debugger appears. From that, I'm confident this crash can be debugged and eliminated.
Jeff Washington
LV R&D
