To help facilitate side by side (SxS) deployments, it would further be nice if VIPM appended the version to the end of the packed project library file (e.g. acme_my_tool-1.0.0.1.lvlibp). This way, I could have several instances side by side in the same root folder:
vi.lib\My Tool\acme_my_tool-1.0.0.1.lvlibp
vi.lib\My Tool\acme_my_tool-1.0.1.5.lvlibp
vi.lib\My Tool\acme_my_tool-2.0.0.9.lvlibp
The great part about crelf's idea is that it further abstracts the management of deployment files (here, an LVLIBP) from developers.
Quick Drop shows the name of the project library, so if the name included the version I can be careful not to select the wrong one. If I do select the wrong one, I'm hosed unless the package developer changes the icon for each release (unlikely). So, lastly, it might make sense to have an option to include the build number somewhere on all VI (and CTL / LVLIBP) icons to reduce the chance of cross-linking.
To help facilitate side by side (SxS) deployments, it would further be nice if VIPM appended the version to the end of the packed project library file (e.g. acme_my_tool-1.0.0.1.lvlibp). This way, I could have several instances side by side in the same root folder:
vi.lib\My Tool\acme_my_tool-1.0.0.1.lvlibp
vi.lib\My Tool\acme_my_tool-1.0.1.5.lvlibp
vi.lib\My Tool\acme_my_tool-2.0.0.9.lvlibp
The great part about crelf's idea is that it further abstracts the management of deployment files (here, an LVLIBP) from developers.
Quick Drop shows the name of the project library, so if the name included the version I can be careful not to select the wrong one. If I do select the wrong one, I'm hosed unless the package developer changes the icon for each release (unlikely). So, lastly, it might make sense to have an option to include the build number somewhere on all VI (and CTL / LVLIBP) icons to reduce the chance of cross-linking.