This is something that would be a great addition for those of us working on different platforms (i.e. Windows and RT).
When a VI is compiled for a particular platform, add a seperate area to the actual VI file to keep the platform dependent compiled code. This way a vi that has been compiled for use on windows and for RT would have two sectons that keep a seperate copy of the actual machine code for each OS.
Where this issue becomes a problem is when you have common code called from a project that has both Windows and RT components. This creates an endless recompile operation as code is built
As an example:
Code is compiled for Windows.....windows machine code is generated and saved in the vi
Code is opened under RT.....changes pending because the compiled code does not match the platform
Recompile vi for RT....RT machine code is generated and saved in the vi.
When the code is reopened under Windows, it requires another recompile due to the existing RT machine code.
Obviously any changes to the FP or BD would cause all of the machine code areas to require a recompile.
This would add more size to each individual VI, however disk space is relatively cheap with respect to LabVIEW development systems.
) *(see footnote)
