08-23-2018 10:31 AM
Sorry if this is the wrong place. My company does lots of different types of software development, and has internally standardised on VSTS (I think this is the replacement for TFS) for issue and config control.
I'm prepping for a big LabVIEW project, and apparently need to integrate this into our standardised process. But I'm not sure how to do it - our VSTS sits on a server somewhere, but when go to the LabVIEW options to configure source control, there is nothing for me to select in the drop-down box. Presumably this is because I don't have VSTS installed locally to my desktop machine, but then that's pretty normal, I think.
How can I bridge the gap? I don't want to lose the ease of config control because of a standard tool, but apparently our QA people frown on us deviating from our standard process.
Solved! Go to Solution.
08-23-2018 11:00 AM
VSTS is not natively supported in LabVIEW. Nor, can I recall a 3rd party toolkit for that.
So, it's a roll you're own Framework you can write, if you know how. Look into the Framework providers group on the community side for help getting started.
09-10-2018 07:53 AM
Thanks for this - think we will go with on-premises TFS and then hook into that using a git client.