automated, scheduled, overnight build

[nathanb]

Hi,
I am interested in building an application overnight while I am out of the office (this overnight build will occur along side of a larger build process involving VB project). Is there any way of automating the LabView General build process (I'd even like to log any errors created during the build process to a file).
Thank you for your help.
Nathan

[Labviewguru]

Nathan,

I have just looked at the VI Server, and found that you can actually do mass compiles using the VI server. However, as the application builder is a seperate application, I don't know of any way that you can automate that. I would check with NI to see what they know. I highly suspect that there isn't anything out there.

I would also suggest an alternative, if possible, to your build method. I have had, in the past, issues with packaging my entire hierarchy into a single executable (DLLs are the only things I have had success with). I would recommend that you consider building the application using a "Loader" program. The loader uses VI server to load and call your VI Hierarchy. This makes a lot of things easier, is more reliable, and mak
es integration much easier. However; only you can determine if this is the way to go. I will say that I had a lot of success with it, especially in that some of the VIs for the project had to be modified on occasion. Just the work saved in not having to keep rebuilding the application made the Loader method worth while.

Feel free to email me if you would like more information about the loader. I can also post it here if you like. (My email address is in my profile.)

Good luck

[AIR]

Hi,

This is how I would (try to) do it, but it won't be nice....

The application builder is just a vi. It's in the llb called
prodisttool.llb, the vi is called Build Application.vi. So theoreticaly, it
is controllable with VI server.

Unfortunatelly, the vi is password protected. This makes it nessesary to use
VI server. Also, the VI may use shift registers to store data, so a lot of
testing will be needed.

This is the way to build an application;

Open the VI with VI Server.
Press the Load button with VI Server, won't work, because a windows diolog
comes up.
So, fill in everything seperatly.
You could perhaps automate this, by getting all values with VI Server, and
using these values to set all controls when needed.
Press Build with VI Server.
Make sure there are n
o popups during the build.


It won't be easy, but I think it's doable!

Good luck,

Wiebe.








"nathanb" wrote in message
news:5065000000080000009B3A0000-1011517314000@exchange.ni.com...
> Hi,
> I am interested in building an application overnight while I am out of
> the office (this overnight build will occur along side of a larger
> build process involving VB project). Is there any way of automating
> the LabView General build process (I'd even like to log any errors
> created during the build process to a file).
> Thank you for your help.
> Nathan

[AIR]

Hi,

This is how I would (try to) do it, but it won't be nice....

The application builder is just a vi. It's in the llb called
prodisttool.llb, the vi is called Build Application.vi. So theoreticaly, it
is controllable with VI server.

Unfortunatelly, the vi is password protected. This makes it nessesary to use
VI server. Also, the VI may use shift registers to store data, so a lot of
testing will be needed.

This is the way to build an application;

Open the VI with VI Server.
Press the Load button with VI Server, won't work, because a windows diolog
comes up.
So, fill in everything seperatly.
You could perhaps automate this, by getting all values with VI Server, and
using these values to set all controls when needed.
Press Build with VI Server.
Make sure there are no po
pups during the build.


It won't be easy, but I think it's doable!

Good luck,

Wiebe.








"nathanb" wrote in message
news:5065000000080000009B3A0000-1011517314000@exchange.ni.com...
> Hi,
> I am interested in building an application overnight while I am out of
> the office (this overnight build will occur along side of a larger
> build process involving VB project). Is there any way of automating
> the LabView General build process (I'd even like to log any errors
> created during the build process to a file).
> Thank you for your help.
> Nathan

[AIR]

Hi,

This -might- be an easier way of doing it;

Create a new ActiveX automation ref. (use communication>ActiveX>Automation
Open.vi)
Right click 'Automation Refnum' and select (from the Type Library) 'LabVIEW
DLL Builder ActiveX Automation Server Version 1.0'
Use 'Invoke Nodes' to create a new project, open an existing project, and
build.

This is not documented at all, but should work if used correctly...

Regards,

Wiebe.





"AIR" wrote in message news:a3b854$i85$1@news1.xs4all.nl...
> Hi,
>
> This is how I would (try to) do it, but it won't be nice....
>
> The application builder is just a vi. It's in the llb called
> prodisttool.llb, the vi is called Build Application.vi. So theoreticaly,
it
> is controllable with VI server.
>
> Unfortunatelly,
the vi is password protected. This makes it nessesary to
use
> VI server. Also, the VI may use shift registers to store data, so a lot of
> testing will be needed.
>
> This is the way to build an application;
>
> Open the VI with VI Server.
> Press the Load button with VI Server, won't work, because a windows diolog
> comes up.
> So, fill in everything seperatly.
> You could perhaps automate this, by getting all values with VI Server, and
> using these values to set all controls when needed.
> Press Build with VI Server.
> Make sure there are no popups during the build.
>
>
> It won't be easy, but I think it's doable!
>
> Good luck,
>
> Wiebe.
>
>
>
>
>
>
>
>
> "nathanb" wrote in message
> news:5065000000080000009B3A0000-1011517314000@exchange.ni.com...
> > Hi,
> > I am interested in building an application overnight while I am out of
> > the office (this overnight build will occur along side of a larger
> > build process involving VB project). Is there any way of automat
ing
> > the LabView General build process (I'd even like to log any errors
> > created during the build process to a file).
> > Thank you for your help.
> > Nathan
>
>