Labview 2013 + Windows7, can't add file to llb

[Abdulaev_Rustam]

---

@Larry.C wrote:

Hi,

Could you possibly add the LLB file and the VI to a project? Then drag the VI in the project into the LLB and save the LLB.

Kind Regards,

---

Hi Lary,

I was quite happy with old way of managing LLB files, without opening project manager and other stuff.
If it is possible to do with one click of the mouse why should I spend 10 clicks to do the same?
It looks like some of your developers are infected with an obsessive idea to make my life harder with "Microsoft-style" innovations"?
No thanks, I want back my old and reliable labiew with intuitively clear interface.

[Larry.C]

Hi Abdulaev,

The reason LabVIEW has moved towards the use of projects is because it is an essential tool to manage applications. I would not recommend developing an application without the use of a project. Projects can check for and resolve conflicts, they are required for building executables/installers and provide loads of other functionality. I do not believe it would take much time to port your application over to a project and I think you will start seeing the benefits straight away.

Kind Regards,

[Abdulaev_Rustam]

---

The reason LabVIEW has moved towards the use of projects is because it is an essential tool to manage applications. I would not recommend developing an application without the use of a project. Projects can check for and resolve conflicts, they are required for building executables/installers and provide loads of other functionality. I do not believe it would take much time to port your application over to a project and I think you will start seeing the benefits straight away.

---

Hi Larry,

I appreciate your answer, but I already tried to use projects and didn't find any advantages to me.

And Yes, you may consider that as customers' feedback.

[Larry.C]

Hi Abdulaev,

I am sorry you did not find the project to be useful. We always appreciate feedback as we can then try to suit as many peoples needs from the environment as possible. I will pass this feedback on to the relevant channels.

Kind Regards,

[HoussamK]

Hi

Best Practices for Managing NI LabVIEW Applications Using the Project Explorer

This article examines the LabVIEW Project and provides recommendations for how to manage and organize your LabVIEW applications.

If you want to build an LabVIEW EXE or Installer you will need the Project Explorer.....

[HoussamK]

During the development phase, LabVIEW users work to translate the software design into working LabVIEW code. As an application grows larger, developers need tools to help manage the files associated with the application, such as VIs, documentation, third-party libraries, data files, and hardware configuration settings. Engineers can use the LabVIEW Project Explorer  to manage such files.

[geirove]

NI: in LV 2009 and 2010, I have NOT been able to use the Project Manager (PM) due to extremely slow performance: I think it happened after adding an ActiveX Component: The Calendar. However, I have a project of > 1000 VIs (see www.objective.no/lean), and I am doing all my development outside the PM.

I am resorting to all kinds of 3. party tools to be able to navigate my code, since NI is not capable of inventing a VI Browswer where I can sort what to see (e.g. only Block Diagrams), set bookmarks and favorites.  (Search & Replace, WinLister etc).

I have even created a Script that compiles and names my APP without opening the PM: I only open the PM occasionally when I have to. However, I do want NI to provide an efficient PM, but the current versions of the PM are not effcient to use!

For years OO enviroments (Eclipse, Smalltalk) have had excellent tools to manage Source. Isn't it about time LV gets the same?

If I have 15 VIs open, the Task Manager shows 30 entries: One for each Front Panel, and one for each Block diagram. This is counter-prodictive indeed.