VIPM Package Builder with Preserve Directory Hierarchy Problem

[cirrusio]

Hello all,

Trying to figure out a little problem with respect to VIPM package building (v2017.0.0f1).  I had successfully deployed a package previously with no problems but then had to remove, rebuild and redeploy the package due to on-going development and cross-linking issues resulting from that development.  

I solved the cross-linking issues and everything appears to build and deploy ok, but now I have a weird issue where the directory hierarchy is not being preserved despite selecting that option under `Destinations`.  Some of the VIs are being dumped into the top-level deployment folder.   Most (all?) of these VIs are associated with classes.  Does anyone have any thoughts as to what I might be missing that could be causing this behavior?
Thanks

[Mike.B]

Does this issue occur when deploying other packages with directory hierarchies, or just this one? Can you please include screenshots of the hierarchy you're seeing versus the one you expect to see?

[cirrusio]

Thanks for the reply, Mike.  This seemed to be happening with just this package.  Unfortunately, this package is a foundational package so all others depended on it.  This was the first time I saw it.  It seems to have magically fixed itself now.  Not sure what was going on, but I ended up deleting the existing package then rebooting the OS; it seems that something was being cached that was causing this?  I had tried previously just deleting the package and restarting LV but this didn't do it.

Wish I could provide more feedback on this, but VIPM is pretty cryptic with its messaging and very good as misdirection so I have no further information as to why this might have happened.

[Mike.B]

Great to hear the issue resolved itself! Thank you for reporting the result.