Are there disadvantages to using project libraries to organize common code used by different projects?

DOjala · ‎08-26-2014

My company is trying to determine the best way to organize and share our common code. We are using subVersion. We have multiple large programs that are deployed on different machines, some of which are running older versions of labview. I've read a lot of material on how to share code, but I'm still not sure if it makes sense to use project libraries to organize code which will be shared by multiple projects. Another option is building packages. Can anyone comment on the pros and cons? Thank you.

crossrulz · ‎08-26-2014

Because you are using multiple versions of LabVIEW, go with the packages.

Project libraries are saved in a specific version of LabVIEW. So if somebody saves it in 2014, you can't use it in 2013.

If you use packages, then you have a base library that is "installed" for a specific version of LabVIEW. Each version you of LabVIEW can have its own installation of that package.

There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5

LabVIEW

Are there disadvantages to using project libraries to organize common code used by different projects?

Are there disadvantages to using project libraries to organize common code used by different projects?

Re: Are there disadvantages to using project libraries to organize common code used by different projects?