Paths - Development Guidelines / Strategy

[Rashid-Malik]

Dear friends,

I have just finished a project and am going through a resting phase. During this time I want to come up with a paths related strategy that would help resolve all

issues while the project is running in development mode, and while its being tested as an executable (usually at the end of the development phase) and 

when its been bundled into an installer for deployment at the clients PCs. What would be the best stategy that would keep the project errors / problems free

with respect to all three phases. I (we) always seem to run into these problems when we have to turn the project into an executable. Also what is the best

folder structure hierarchy scheme that would cause none or least path related problems for projects. Can you direct me to articles that have discussed these

issues thorougly.

I'll be so thankful!

Have a very pleasant day!

[Ben_S]

C. DOT,

Hello! This Tutorial, Best Practices for Managing NI LabVIEW Applications Using the Project Explorer, should prove very helpful in providing information on project and application structures.

Also, here are numerous Videos, Knowledge Base Articles, and Tutorials on our website that may provide some other additional information and tips about this topic.

Software Engineering Practices for LabVIEW

How to Display File Path Information for the Contents of a LabVIEW Project
Moving VIs in a LabVIEW Project to a Different Windows Folder
Changing the Location of an Additional Installer in My LabVIEW Project
Path Information When Searching For SubVIs

Ben Sisney

Applications Engineer
National Instruments

[Rashid-Malik]

Hello Ben! A reply from you is always a source of contentment and is always of great value. Thanks a lot. I'll go through each and every one of links provided by you. I'll bug you again if some points still requires quenching.

Have a very, very pleasant day!