I currently create a vip that requires a .NET configuration file when the user installs the package. This is known, and expected, since I'm calling certain NI VeriStand .NET assemblies and they need to re-link if I'm installing on a machine with differing versions of the assemblies than the package was created with.
So, currently, I provide users with a .NET config file for their version of VeriStand, have them place it next to LabVIEW.exe (for the version they're installing for) then install the vip. This works great. However, it's a bit of a manual process and means that I have to create and supply a new .NET config file for every release of the .NET assemblies. The obvious solution is to programmatically create the .NET config file using VIPM's Pre-Install VI. The problem, though, is I then need to restart LabVIEW so that it see's the .NET config file and uses those assemblies when it mass-compiles. And I've had problems in the past when LabVIEW is closed during the vip installation.
So, main questions, before I go through the trouble of creating/testing it out:
1. Can you restart LabVIEW from the Pre-Install VI without locking up or upsetting VIPM? My assumption is it won't like losing its reference to the environment.
2. If not, is there a better way to accomplish this? Does VIPM have any built in mechanism for using .NET configuraiton files with packages?
Appreciate any thoughts/ideas!