Stobber 38 Report post Posted March 15, 2016 (edited) I'm walking through a LVRT Project using the VI Server API, trying to find a particular build spec on my FPGA target. I can get the target ("FPGA Target") by name and use that ref to find the build spec by its name, but the reference returned can't be cast to type ProjectItem:BuildSpecification. If I probe the reference wire, the only interesting thing I see is the type GUID... {F4C5E96F-7410-48A5-BB87-3559BC9B167F} Does anybody know of a way to deduce the VI Server object type from this GUID so I can perform a downcast on it? Edited March 15, 2016 by Stobber Quote Share this post Link to post Share on other sites
shoneill 97 Report post Posted March 29, 2016 Good luck with that. A lot of these things are simply not supported in LabVIEW. I don't think you'll be able to get far on this. But if you do, I'd also be very interested in that. 1 Quote Share this post Link to post Share on other sites
shoneill 97 Report post Posted March 29, 2016 What I mean by not supported is that there's no object available to cast it to. Quote Share this post Link to post Share on other sites
Mellroth 65 Report post Posted March 30, 2016 I'm walking through a LVRT Project using the VI Server API, trying to find a particular build spec on my FPGA target. I can get the target ("FPGA Target") by name and use that ref to find the build spec by its name, but the reference returned can't be cast to type ProjectItem:BuildSpecification. If I probe the reference wire, the only interesting thing I see is the type GUID... {F4C5E96F-7410-48A5-BB87-3559BC9B167F} Does anybody know of a way to deduce the VI Server object type from this GUID so I can perform a downcast on it? I might misunderstand what you are trying to do, but do you really need the GUID conversion? Once you get to the BuildSpecs and its OwnedItems you can query each OwnedItem for the TypeString. This typestring is different depending on if you have a build script that is EXE, Source Distribution, Zip etc., but you can cast any of them to BuildSpecification. /J Quote Share this post Link to post Share on other sites