Deployment same computer

[Rafi2003]

Hi,

I have never done any deployment and from what I've read, it's basically aim for installing in a computer where no TS/CVI is installed.

Before I get to this stage I would like to deploy my application in the same computer. The reason is -- I have a working application and would like to save it for "real work" while I'm still improving it and change things in a different place.

I don't like to just copy all the source files to another application but rather create an executable file that will run the application.

How can it be done?

Thanks
Rafi

[Aaron B.]

Hello Rafi,

That is just fine. There is no reason why you cannot install on your own computer. There are certain options that you will not want to enable (ie: if you have LabVIEW already on that computer, do not install support for the LabVIEW Run-time Engine). But in general, there is no problem with creating an installer and installing on the same computer.

If you are asking how to create a deployment system, the best place to start looking is the TestStand Reference Manual. Chapter 14 exclusively discusses this topic in great detail.

Regards,

Aaron B.
National Instruments

[Rafi2003]

Thanks Aron,

Another general question regarding deployment

1) After completing my project in a satisfactory way how do I de-activate my TS3.0+CVI7.0 programs in order to use them on another PC?

2) Will I have any development capabilities at all? If not, will the practice be: to make the change on another PC, create a deployment diskettes and install them on the first PC? It sounds very inconvenient....is this how everybody does it?

Thanks
Rafi

[AllanS]

Rafi,

I am not sure I totally understand you first question correctly. You don't have to deactivate anything to distribute it. For teststand you will have a deployment license and when you activate TestStand with that license it will make it so you cannot do any development. With CVI you will simply distribute the CVI Runtime engine and that will allow you to run all your CVI modules. I feel like maybe you were asking something else. let me know

Next, with a deployment license you will have no development capabilities so you will have to make changes on your design computer and redeploy. Beyond licensing reasons if you could make changes on your deployed system then you could easily lose consistency between different deployments.

Let me know if there is more I can help you with.

Allan S.
National Instruments

[Rafi2003]

Hi Allan and many thanks for your answer

My first question was regarding deactivating the programs CVI7.0+TS3.0 in order to install them on another computer.

I developed my program on a PC which I choose to keep as the tester PC. In this case, according to the license agreement (and the activation rules) I need to deactivate it (or uninstall the programs) so I can install them on another PC and reactivate them. Am I right?

I understand, of course, the other option of installing the deployed system on a new PC (with no NI software on it) and thus, continuing my development on the original PC. The problem with this way is that I need to move my GPIB card along with other hardware (such as DigiBoard) and further hardware adjustments for the new PC.

Which way it preferred and most practiced way?

Thanks
Rafi

[AllanS]

Rafi,

Either way will certainly work. For the first way you will need to deactivate the develpement licenses for TestStand and CVI then Reactivate TestStand with a deployment license. As far as which is the prefered method it really depends where you want to spend your time. If you think it is much more time consuming to move all the hardware then by all means turn your design computer into your test computer and reinstall the software on another computer.

Bottom line, which ever you think will take you less time to get up and running. Let me know if there is more I can do. Have a great day!

Allan S.
National Instruments