Deployment in a network

[Schwede]

Hello,

I have a problem to deploy a teststand system in a network. We have two PC one developer (this in the developer side) and one deployment (it is in the factory side). Both are connected in a network and in this network is an drive (not on one of these maschines) for testing. We need to change the test sequences and modifiy and develop new vi (steptypes). I don´t want to create and install an exe file. I have tried to copy the sequences files and vi´s but then I received an error that other vi´s (which are needed) are not present. Now I use the deployment tool and create a target directory on the testing drive but this is to slow for making littel changes.
I want to modifiy the testsequence, vi´s and steptypes from the developer side and start this sequence directly from the deployment side without using the deployment tool. And I want to use the testing drive on the network.
How can I do that? What is the best way to deploy testsystems in that way?

Greetings

Kai

[Dennis_Knutson]

What I do is first create a new steptype in LabVIEW and once debugged, build it into a DLL. I use DLLs so that I only have to have LabVIEW run-time installed on the production testers. I store all of the custom steptypes on a shared network drive. A sequence is developed and when ready for release, moved to the same shared network drive. We use source code control and all development is done by checking it out of the source code control into a non-production drive. Anyway when a new sequence is released, all that has to be done is reload the sequence on the production tester. When I release a modified steptype, I first have to first unload all sequences that might be using it. You can also create steptypes and save them into an llb and store those on the network drive.