I'm a big fan of source code control. I try to keep everything from LabVIEW code, to drafts of papers, and even PowerPoint presentations in source code control. As a result, it's been years since I last had that heart-sinking feeling of "oh-no... I lost that document"All the work we do at NI is managed in Perforce, but last week I had some free time and decided to make the switch to TortoiseSVN on my laptop to see what all the excitement is about. The switch inspired me to ask you, the community, what you're using and what your experience has been in the hopes of learning more and getting insights into what we can do better.So, what source code control do you like? Do you use the integration tools with LabVIEW? Any other thoughts or details you have to share? We're listening!

ni.com is currently undergoing scheduled maintenance.

Some services may be unavailable at this time. Please contact us for help or try again later.

LabVIEW Development Best Practices Discussions

What Source Code Control Are You Using?

I am using Visual source safe. And I love it. I had to change to ToroiseSVN and Puch ok . I really did not like it. I can back to VSS. But I have to find a another tool. Vss is ending...

Message 31 of 32

(1,823 Views)

Whatever you do, please don't use Visual SourceSafe. Think of the children.

Message 32 of 32

(1,823 Views)

LabVIEW Development Best Practices Discussions

What Source Code Control Are You Using?

Re: What Source Code Control Are You Using?

Re: What Source Code Control Are You Using?