Production environment Vs. Development Enviroment

[oskretc]

Let me start with some context

 

We have to differentiate from a Production environment (to produce data) and Development environment (to develop test and debugging).

 

Our code (very simplified) is organized in this way

 

- Tests (Actual vi that will produce results)

- System files (support vi, drivers, common functions etc.)

 

 

Both are under source control

 

We have decided to make VIPM's (residing in vi.lib) for all System files and leave the Tests files where they are (random folder under source control).

 

This means the all the vi's inside Tests will have links to the System Files (inside vi.lib now) and that works pretty well for the Production Environment, but when we want to use the Tests in the development environment (Tests and System Files in a random folder) we need to re-link all the Tests to point to the local files and not the System Files inside vi.lib.

 

The question is:

 

Is there any way to manually update the references of the Tests so we can choose from where we want to get the System Files?

 

 

[soupy]

Short answer is no. you can't easily modify dependency locations.

 

Longer answer is yes. you can modify environment search paths to point to the new target and delete the old target files to force re-linking, but this is really the hard way and it's going to get you into re-linking trouble/hell.

 

Correct answer is that you're not using vi packages correctly. The code that goes into a VI package should be able to stand on its own. You should be able to debug/test/validate all VI package source code before you build it into a package. Think of a VI package as formally released reusable source code. If you feel the need to constantly switch between built packages and source code, then you're not adequately validating/testing before building the package.

 

Hope this helps.