If everyone is on the same version, then compatibility isn't much of an issue on a day-to-day basis and you have a number of years (10+?) before your code will be obsoleted by an upgrade. Version 2021 would be a good peg if you are looking to freeze the version. If a volume licence is used, it can be easier to manage this than single licences. With large teams this is onerous but not insurmountable. Source control systems treat LabVIEW as binary so all members are forced to update to access the commit or the idiot that did it is forced to back-save and recommit. If one person updates their version and commits to the source control, others using a lower version cannot use that commit. When in teams, updates must be synchronised so that everyone is using the same version. This isn't much of an issue internal to teams but it is when distributing code outside or publicly. LabVIEW is fairly unique in this regard and there are few, if any, that offer this feature-especially with 32 and 64 bit versions. Therefore, if you producing tools for others to use, it is desirable to use the minimum version so that all forward versions can use it (bugs aside). LabVIEW is backward compatible over many versions but is not forward compatible. I like to let those that must have the latest and greatest find the bugs Generally, I will not use a version of LabVIEW on a project unless it is 1 year old or a customer demands it. Many projects have failed to meet the deadline due to this-I know from experience. One of the worst things to do is to update half-way through a project and find out everything falls to pieces. You can consider this a micro version of what you are proposing. It should also be noted that I do have all versions (32 & 64 bit) from 2009 through to the latest that the final product is tested with. When producing code for customers I freeze versions on a per-project basis. While I don't have access to the latest and greatest features, compatibility is the main reason followed by robustness of that version. I use LabVIEW 2009 for all my development.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |