Potential bad build / vi location issues

[Tyfosho]

Two machines, running LabVIEW 2018, installing DCAF Core from VIPM.

Trying to open the Temperature Control Example presents dialogs to find missing VIs/classes.

The example is looking for:
LabVIEW 2018*Targets*\vi.lib\NI\DCAF\Tag Editor Core\control module\configuration\control module configuration.lvclass - This class does not exist on disk, However LabVIEW 2018\vi.lib\NI\DCAF\Tag Editor Core\control module\configuration\control module configuration.lvclass, does.

LabVIEW 2018*Targets*\vi.lib\NI\DCAF\Modules\CVT Access\execution\CVT runtime.lvclass - This class does not exist on disk, However LabVIEW 2018\vi.lib\NI\DCAF\Modules\CVT Access\execution\CVT runtime.lvclass, does.

LabVIEW 2018*Targets*\vi.lib\NI\Model Execution Interface\Engine Configuration\engine configuration.lvclass - This class does not exist on disk, However LabVIEW 2018\vi.lib\NI\Model Execution Interface\Engine Configuration\engine configuration.lvclasss, does.

[Tyfosho]

This appears to be an issue with 2018. Installing on a 2017 machine has no issues

[pjrose]

Just installed DCAF Core 1.3.0.12 on LabVIEW 18.0f2 (32-bit) with VIPM 2018.0.0f1. No problems encountered during install. Had to manually step through the graphviz installer (next, next, ok, next), although the vipm started it for me. "Temperature Controller Example" loaded fine immediately after.