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
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 Building Guide
Comments
2 comments
LabVIEW VI Server Settings - Make sure you have the following VI Server settings in your LabVIEW Options. Note that the Port number will be different on your system (five nights at freddy's online). If you have multiple LabVIEW versions, then you should assign a different port number for each LabVIEW version. Normally you should not have to adjust your port numbers since VIPM will set these automatically
To keep track of and manage changes to drift hunters your VI Package build settings and package configuration, you'll want to know how these capabilities integrate with your Source Code Control (also known as Software Configuration Management) system.
Please sign in to leave a comment.