When a LabVIEW project is opened, not all VI's within the project are immediately loaded into memory. I believe this becomes an issue with the LabVIEW Solution Builder because when the Replace With operation attempts to keep the changes in memory, the VI's that are not immediately loaded into memory immediately leave memory after the Replace With operation completes. This results in the potential coexistence of the lvlib and lvlibp versions of the dependent libraries in the dependencies for a project that may not always cause errors that break the build.
This issue can be recreated by manually tracing the process that the Solution Builder follows, and to the best of my knowledge there is no code in the Solution Builder that ensures the VI's I referenced above stay in memory until the build is complete. For this reason, I believe it would make sense to add a feature that ensures all VI's within a project are fully loaded into memory before the replace operation and that they remain in memory until the build it complete.
I welcome any feedback on this idea. Please let me know if you have any questions or if you would like me to provide a specific test case. Thank you.
When a LabVIEW project is opened, not all VI's within the project are immediately loaded into memory. I believe this becomes an issue with the LabVIEW Solution Builder because when the Replace With operation attempts to keep the changes in memory, the VI's that are not immediately loaded into memory immediately leave memory after the Replace With operation completes. This results in the potential coexistence of the lvlib and lvlibp versions of the dependent libraries in the dependencies for a project that may not always cause errors that break the build.
This issue can be recreated by manually tracing the process that the Solution Builder follows, and to the best of my knowledge there is no code in the Solution Builder that ensures the VI's I referenced above stay in memory until the build is complete. For this reason, I believe it would make sense to add a feature that ensures all VI's within a project are fully loaded into memory before the replace operation and that they remain in memory until the build it complete.
I welcome any feedback on this idea. Please let me know if you have any questions or if you would like me to provide a specific test case. Thank you.