NI Package Builder - adding external packages to installer

[pitol]

Hi,

I would like to create an installer of my packages created in NI Package Builder.

So far it's easy.

But now I would like to add to the installer a package which is not created in NI Package Builder.

It is an output of TestStand Deployment Utility.

I can add that package to the installer only if I have that package installed (it is then visible in Add Packages -> Installed Packages).

I cannot add that package if it is not installed in my system...

Why?

My idea is that I would like to create an installer from multiple repositories where each repository contains source code for each package.

The only exception would be a package of TestStand distribution... And this exception is killing me 😠

[CL_eisenwr]

From my conversations with NI, one of NI Package Builder uses is to replace the TestStand Deployment Utility. Have you tried creating an NI Package with it that replicates your TestStand Deployment?

[Scott_Richardson]

Hey pitol, you are correct that NI Package Builder only supports adding packages from feeds if they are installed. Pulling arbitrary packages for disk is not supported at this time. However, if a package is a top-level item in a package installer on disk, you can select the installer and select a top-level package from that package installer and include that package in a package installer that NIPB is building. So an alternative to installing the package is to create a package installer in TSDU that includes your package, and NIPB can read it.

[pitol]

Thank you both for your answers.

@Bill

Sure I can recreate TestStand Deployment in NIPB. The TestStand package was prepared some time ago so I though it would be easier to just simply add it to the Installer. Seems not so easy. But I think I will go this way. There is no point for keeping two separate distribution/packages projects.

@Scott

I'm not sure if I understand your solution. Anyway, I will rather "rebuild" my TestStand distribution in NIPB.

Thanks again!

[Scott_Richardson · Accepted solution]

Pitol, the TestStand Deployment Utility has the ability to create a package and a package installer that includes the package. NI Package Builder has the ability create package installers and you can include packages from other package installers on disk. The above might be a lot faster to do than using NI Package Builder to create your original package.

Note that NIPB does not yet support all features in TestStand Deployment Utility and you can refer to the table in the "TestStand Support" topic in the NI Package Builder help.

[pitol]

Now I get it. Thanks!

In that case I will look into both options to see which one is better for me.