viobj files for multiple targets

[gsussman]

The ability in LV2010 to seperate the actual compiled code from the actual source code seems like a nice feature, especially for those of use using source code control.

Will LV now have the ability to maintain compiled code for a single VI and multiple targets? Do we now have the ability to simultaneously have a VI that has been compiled for Windows and RT AND maintains the compiled code for each, or will a single VI only allow the existance of a single viobj file?

I don't have my system set up yet with 2010, but I am curious if NI was able to kill 2 birds with one stone on this feature.

[tst]

I don't know what the final implementation of the feature is like, but that is certainly possible. In the beta, the .viobj files were placed in a high level folder which had the relevant machine info (e.g. x86). I haven't looked at other targets at the time, but it's certainly feasible that this is how it works. I assume the help (which should be available on-line) does make a reference to this, so you can try searching it.

[gsussman]

Not too much help from the help files. No mention of the behavior on multiple platforms

[tst]

This seems to be pretty explicit:

---

Select the object cache for a specific target to delete an object cache.

• Target—Lists the target types for the object caches that you can delete.

---