Programmatically open build spec properties dialog

[michael.lambert]

Has anyone ever figured out how to programmatically launch the properties dialog for a build spec. I have a tool that shows the build specs from all the open projects. From the tool, you can update change logs and build the exe's or installers (which will be archived). I want to add a button that will open the build spec properties dialog, in case they want to go in and change things like debugging or always included files.

Note, I do not want to add all of these functions to my small tool, I'd much rather launch the dialog.

I dug around and found an "Open Build" VI in the "NI_AB_API_Build" Class, but I get a "build specification not found" when I try to open my exe build spec with it (double-checked paths and names).

Any advice? Thanks in advance!

[paul_cardinale]

"Open Build.vi" doesn't open the buildspec properties dialog, it creates a .lvclass object (which probably contains the buildspec).  I couldn't find the thing that opens the buildspec properties dialog.

[WaiLee]

Hi, Michael.lambert

Kindly refer to the attached zip folder below, It contain different examples to build and edit the parameters for build specifications.

Here's the link they might help you understand more on what the attached examples VI doing:

https://www.ni.com/docs/en-US/bundle/labview/page/creating-build-specifications.html

[WaiLee]

Extra note on how I call out a VI and pop it out as dialog box when a Boolean button is detected in event structure:

Remember to click the build VI, go to file>>VI properties>>Window Appearance>> Dialog so that it appear as dialog box when it call out. 

https://www.ni.com/docs/en-US/bundle/labview/page/creating-a-dialog-box.html

[srikrishnaNF]

Hi WaiLee,

Can you please send the code attachment in LabVIEW 2017 version?

[WaiLee]

Alright srikrishnaNF.

Here you go 2017 version.

[michael.lambert]

Seems there might be a misunderstanding here. I'm not having any issues programmatically building applications - which can be done with the NI_App_Builder_API, you don't need to use the command line (change version and build with LabVIEW.png). I also know how to create and configure a VI to work as a dialog. 

What I'm asking is if there is a way to launch the already existing build spec properties dialog for a build spec that I specify (see Build Spec Properties Dialog.png). I load the build specs from open projects into a drop-down list for the user to choose from. When the select one, it will display the version number and allow them to edit it. But if they want to edit other properties, such as the "always included" files or "source file settings", I'd like to have an "Open" button that will launch the build spec properties dialog (example in Open Build Spec button.png)

If figure this dialog has to live somewhere, in a DLL or otherwise and there's most likely a way to launch it without having to go through the project. But perhaps not!

[michael.lambert]

Yeah, that makes sense. Let me know if you end up coming across it later!

[natasftw]

---

@michael.lambert wrote:

What I'm asking is if there is a way to launch the already existing build spec properties dialog for a build spec that I specify (see Build Spec Properties Dialog.png).

---

As a curiosity, how much time have you spent so far trying to find this?

Do you want your users to have access to ALL of the options or just a subset including those you've listed as an example?

I ask these as it sounds like the answers would lead towards a quick recreation in your tool being less time to handle and give you more control over what is being done.  While that's not what you've explicitly asked for, I'm curious as to why it isn't the desired outcome.

[michael.lambert]

---

@natasftw wrote: As a curiosity, how much time have you spent so far trying to find this?

Do you want your users to have access to ALL of the options or just a subset including those you've listed as an example?

I ask these as it sounds like the answers would lead towards a quick recreation in your tool being less time to handle and give you more control over what is being done.  While that's not what you've explicitly asked for, I'm curious as to why it isn't the desired outcome.

---

 I've spent maybe four hours over a couple of days looking through the App Builder API folders, trying different things, and looking on the forums. I would like them to be able to access all the properties. The tool I'm making is really just for building and archiving applications. Adjustments to the build properties should be done from the native dialog. So I'll probably just abort this and just add a button to bring the selected project window to front. 

Thanks