I'm declining this - the move towards package based installers should provide a better solution that allows people to structure packages to not install over development files.
I have seen multiple customers who have encounter the following error:
Error: The following VIs or Project Libraries have duplicate names You must change the names or add them to project libraries:
The issue sources from installing a TS deployment onto your development machine. It is not recommended. And though the deployment will be able to execute, it can also cause undesired linking errors, as shown in these cases. As a result, some of the VIs called are looking to SupportVIs (even in your development sequence), and other VIs called are looking for the same named VI in vi.lib. There can't be two different VIs with the same name, unless they are in two different libraries.
I suggest that we implement a warning when such an installation is started or even an error which prohibits installation fo the deployment.
Shawn S. | NIC Instrument Driver/IVI PSE National Instruments