Jump to content

MrShawn

Members
  • Content Count

    2
  • Joined

  • Last visited

Community Reputation

0

About MrShawn

  • Rank
    I've come back for more.

LabVIEW Information

  • Version
    LabVIEW 2017
  • Since
    2017
  1. Hooovahh, thanks for the response. When you say "I just suggest Tortoise SVN" by that do you mean tortoiseSVN versus other client side options or are you saying do not use the TSVN Toolkit from viewpoint (http://sine.ni.com/nips/cds/view/p/lang/en/nid/211524)? While merge is the ideal, we would likely use the lock/commit scheme, but a concern is, Dev. A is working on a control or enum that cascades down to multiple VIs will that developer need to lock out all of those VIs from Dev. B? It seems like the best way to avoid lockout issues is with branches but my concern is how well these branches can be committed back to the main trunk for deployment, particularly for Labview. Again, thanks for the response, a lot of good information and advice. -MrShawn
  2. Hi all, I am fairly new to Labview development. I want to implement revision control software (SVN in particular) to my workplace. Before I can do this, I need to prove the concept and usefulness of the SVN application for us. I have used SVN in some degree in the past, and noticed tortoiseSVN integration with Labview via the TSVN Toolkit. I have a few questions regarding SVN and how I should organize my project files, in particular when using SVN. File organization has been a particular gray area for me in Labview, unlike linking my libraries and specifying their locations I don't seem to quite have that control in Labview. This issue is somewhat more exacerbated (or at least so I think) when I began using SVN. Let me explain: Using the TSVN toolkit it sees that my entire class (which was developed in a separate directory - then linked in) is not sourced and revisioned. This is also the case for several other libraries which I have borrowed or developed myself. I have two primary questions regarding this. The first - How does SVN add/commit these project files when they are not present within the project directory itself? In fact I have created a separate repo for the class which I use to maintain that code. The second - Is my file organizational design fundamentally flawed? Especially in the context of SVN? What are some good organizational tips/ schemes (when using SVN) which would help me for future projects in avoiding issues such as this? A less pressing question: How well does the "merge" functioning work with the Labview VIs? Remember I am do not have the most experience with SVN - it is my understanding that merge basically would merge changes I have made back with changes by other devs to the file along the main trunk(?). Thanks in advance. MrShawn
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.