LabWindows/CVI Idea Exchange

About LabWindows/CVI Idea Exchange

Do you have a feature idea for how to improve LabWindows/CVI? Submit and vote on ideas now!
  1. Browse by label or search in the LabWindows/CVI Idea Exchange to see if your idea has previously been submitted. If your idea exists, be sure to vote for the idea by giving it kudos to indicate your approval!
  2. If your idea has not been submitted click New Idea to submit a product idea. You should submit a separate post for each idea. Watch as the community gives your idea kudos and adds their input.
  3. Give kudos to other ideas that you would like to see implemented!
  4. NI R&D will review ideas that have been submitted and update the status.

Note: the LabWindows/CVI Idea Exchange is not the appropriate forum to submit technical support questions.

The LabWindows/CVI R&D team is committed to reviewing every idea submitted via the LabWindows/CVI Idea Exchange. However, we cannot guarantee the implementation of any LabWindows/CVI Idea Exchange submission.

Top Kudoed Authors
User Kudos Count
Showing results for 
Search instead for 
Did you mean: 

Add official support for GIT

The integration of some SCC software is officially supported in CVI (see this KB).

Unfortunately GIT is not officially supported, but its popularity has been increasing very much.

LabVIEW has a specific User Group in the community (Git User Group) and I think CVI should support the same integration


In claris non fit interpretatio

Using LV from 7
Using LW/CVI from 6.0



Why don't you just use git from the command line? If you'd rather have a fancy UI, there's GitEssentials which is pretty powerful. Of course I see the appeal of having integrated scc support, but on the very very very long list of features that should be implemented, git integration probably is rather at the end.


The big issue with cvi and GIT and even SVN is when you try and merge, especially the user interface in CVI, say for example you have two people that make a change or add to the user interface. when you go and merge the two programs together this becomes a nightmare in having  to go in line by line of the .tui file and try and seperate the two changes out. Regardless the only service for repositorys that cvi is supporting is Preforce, Subversion. People want to have the option to use different revision software that can be used and implemented on there own server, without using a offsite service and one that is free.