Search the Community
Showing results for tags 'project templates'.
Found 1 result
For a lot of my LabVIEW projects, I have been developing scripting tools to help team members get to a good starting point for their code or to remove human error when following templates. After seeing Becky Linton's presentation at NI Week in 2016 (link), I was inspired to use Project Templates to make it a little easier for the developers to get to. I have been able to get it to work to varying degrees at this point, but I have a question on how to handle project-specific dependencies. If I have a team working on a larger development project that has shared core code and we have it in a repository, everyone on the team usually puts the cloned source on a different location on disk. If my scripting tools have a dependency on code in that repository (class ancestor is biggest), then its location would move from development machine to development machine. Therefore, if I put my tools into the LabVIEW\ProjectTemplates directory, those dependencies would need to re-map for every user and that defeats the benefit to having it be a part of the Getting Started window - at that point it is easier just to point them to the scripting wizards that are pulled with the rest of the code from the repository. Does anyone have a good suggestion for how to accomplish a good structure with project-specific dependencies? Or am I trying to fit a square peg into a round hole for this type of application?