NI Package BUILDER --> How to handle duplicates

[Oli_Wachno]

So here's my use case:

I have an own ProjectTemplate to integrate into LabVIEW, so it shows up under File-> CerateNew...

I want to deploy it on computers using an NIPKG during our NIPM based software rollout. I need to install it in both the 32 and the 64 Bit version of LabVIEW.

Attempt 1.) Add the template code in the input pane and assign multiple locations for the files --> error, doesn't work

Attempt 2.) Duplicate the template code into a seperate folder on disk, try to assign the files to from one folder to the 32Bit LabVIEW folders, the others to the 64Bit --> error due to file name duplicates

Attempt 3.) Define a seperate 64Bit package within the same solution, --> error due to file name duplicates

I could create a new solution, but this would kinda interrupt my workflow....

Any ideas for an alternative approach?

Cheers

Oli

[Scott_Richardson · Accepted solution]

Oli, when I was at NI with NIPB we did want to support allowing a single file to be deployed to multiple destinations in one or more packages in the solution; however, we never got to it.

Since a system might have only one LabVIEW bitness installed or could have both, you could create two packages, one for each bitness. Your options are:
1. Create a separate NIPB solution per LabVIEW bitness.

2. Duplicate the code on disk for inclusion in the solution (this would work for a single package)

3. Create one solution for one bitness and if automating the build you could build, the default solution, alter/copy solution content to target other LabVIEW destination folder and build.

[Oli_Wachno]

Scott, thanks for the insights!

Guess, I'll go with two sperate packages, but having them created in the LabVIEW project, which actually creates the according Source Distribution.

---

@Scott_Richardson wrote:

[...]

2. Duplicate the code on disk for inclusion in the solution (this would work for a single package)

[...]

---

From what I saw yesterday, this will fail also with a duplicate file name error