Deploying a LabVIEW executable on a machine that already has the LabVIEW environement poses problems. Among those, the LabVIEW runtime is sometimes downgraded by the new install, plus LabVIEW projects sometimes cannot build anymore and display strange errors after installing an unrelated LabVIEW executable.
This has been the case for a long time now (not just the present version), but it is really a pain. That means that we cannot safely deploy executables built with LabVIEW on the machines of customers who happen to have the LabVIEW environement. When the installation corrupts their LV environement, customers are understandably annoyed (to stay politically correct).
Do you think you could find a way so there is no risk installing an executable built with LabVIEW could corrupt the LV environement, when there is one on the machine?
Thank you for your help
Bruno