###Goals: This project should allow people to contribute tools they use on a daily basis for development purposes. For example, this might include quick-drop shortcuts, tools menu items, or other helpful utilities.

###Repository Overview: LabVIEW Development Utilities is the location of the tools menu item that will be added to LabVIEW when the package installs. Other folders contain individual components and are typically installed to vi.lib. The files in "LabVIEW Development Utilities" are simple launchers.

Note: Tools menu items are launched in special contexts. We've seen issues with class loading in these contexts. This loader works around the problem by loading a project (required because a project-specific conditional symbol was used): https://github.com/NISystemsEngineering/LV-Dev-Utilities/blob/master/Trunk/LabVIEW%20Development%20Utilities/VI%20Modifier%20Utility.vi Similarly, the Application.Default.Application property can be used to load items in the Main Application context.

###Contribution Workflow: For a more complete workflow, view this set-up guide and this workflow guide.

1. Fork this repository into your account.
2. Create a branch for your change.
3. Make changes, periodically pulling and merging any updates from the central repository.
4. Push your changes up to your branch in your copy of the repository.
5. Send a pull request to the owner of this primary repository. Follow the contribution guidelines.

###Contribution Guidelines:

• Limit the scope of your change as much as possible. Smaller changes are easier to process. Any major changes should be discussed beforehand with the managers of the repository to ensure that it fits within the goals and vision of the project.
• Explain the reason for your change with as much detail as possible. If it is a bugfix, link it to an issue in the issues tracker. If it is an enhancement, consider making an issue in the issue tracker to discuss the enhancement before making it. This ensures that the enhancement will provide value to other users.
• Run through the style guidelines and any available VI analyzer tests to ensure compliance with the general style of the project. Don't go crazy trying to make the code perfect. Do make sure there are no glaring issues.
• Before committing a change, be sure to rebase or merge your code off of the most up-to-date source in the master. This reduces the risk of merge conflicts and makes it that much easier to merge your pull request and that much more likely that the change will be accepted.
• Ensure that all builds are successful with your change in place, after rebasing.
• Ensure that all tests pass with your change in place, after rebasing.