LLB opening bug

[Dennis_Knutson]

The different platforms make it expensive for you since you need each version but on the other hand, you don't need a LabVIEW license on each pc you deploy to. Where I am now, we have several hundred pc's in a couple of countries that we deploy to. The idea of doing minor code tweaks on even a small percentage of them, makes me shudder. That is one of the reasons we are very specific on the hardware/software that can be used. That includes the pc, the OS, the DAQ board, NIC, modem, etc.

[JasonD_at_UML]

For me, the "expensive" part would be all of the time involved, I have a site license with all platforms, with is really nice to have.
I can see that specifying a particular hardware requirement would simplify things, but alas, I need to support all 3 (ask me about fonts and appearance differences sometime - yuck).

I don't want to depart too far from the original topic of this thread, so I'll leave off here.

Thanks again for the tips.

[Travis_M.]

We used to supply a shell extension to open LLBs in Windows Explorer, but the problem was that this could not work with Vista, so we had to make a change.  We used to make the LLB behavior configurable through the Tools»Options»Environment page, and in some LabVIEW versions (I tested 8.0) we did use the LLB shell extension by default.  We discussed whether or not to make the LLB manager the default, and decided that the majority of users intend to use the LabVIEW development system to edit VIs when they double-click an .llb file, so we decided to enable the LLB manager.  LabVIEW 8.2 had a problem with the shell extension option which may be why it was previously disabled (I didn't specifically test 8.2 though). The behavior was documented in the LabVIEW 8.5 Upgrade Notes (see page 12).  One thing to be aware of, is that the INI key to disable the LLB Manager only works in 8.5.1 (see bug ID 67983 in the LabVIEW 8.5 Known Issues Document).

 

Hope this helps shed some light on the situation-