Hi Forum,
I have two projects once the framework and the product specific project.
These two projects are loaded in separate virtual drives.
From the product specific project a Packed Lib is created which is called at runtime in the Framework.
Both projects have several Packed Libs e.g. Actor Framework.lvlibp, Base_Actor.lvlibp, XControl.lvlibp which are contained in both projects.
These data lie so to speak on each virtual drive as a copy.
Normally the projects are strictly separated from each other. Framework on drive X, project on drive M there are no VIs or other objects which refer to the other drive.
Unfortunately it happens occasionally that LabVIEW means to build links between both projects.
That means in the product specific project a conflict arises e.g. between the Base_Actor.lvlibp of the X and M drive.
LabVIEW has added the lvlibp from the other project to the product specific project in the dependencies.
This causes me to have conflicts within the project.
Currently, I then proceed as follows.
I disable the drive of the framework project.
Open the product project and see which VIs have the wrong lvlibp loaded. Open those and save them again.
Is there any way LabVIEW can fix this permanently.
I am also not clear why under what circumstances LabVIEW occasionally sets up this short cut.
Thanks a lot
