JKI Software

Using VI Package Builder with Source Code Control

Now that you know all about Managing Package Dependencies and Package Configuration Management you'll probably want to know how these features can work with your Source Code Control (a.k.a. Software Configuration Management) system, which will allow you to track and control changes to your VI Package build settings and package configuration.

You might have wondered up to this point, "Where are the build settings and VI Package configuration saved?"

If you look inside your VI Package Source Folder you will notice two files:
  • .vipb - this contains your build settings
  • .vipc - this contains your VI Package Configuration
We recommend that you keep both of these files under revision control by checking them into your source code control system, just as you would all of your VIs and other files in your VI Package Source Folder.



By keeping these files in your source code control system, you can be sure that your changes are backed up and changes are fully controlled.

Congratulations, you've now an expert package building junkie!  Why not start using VI Packages in your organization?  See our Packaging your Reuse Libraries guide for the details.

Up: VI Package Guide

If you have any feedback or questions (including ideas for other topics you'd like to learn more about), please consider posting them to the VIPM Discussion Forums.  We're looking forward to your feedback.

JKI Home > VIPM > Package Building Guide > Using VI Package Builder with Source Code Control

Home | About Us | My Profile | Privacy | Legal | Contact Us | © 2006-2008 JKI. All rights reserved.