Context handling in LV 2025 Q3

[Intaris]

I've recently moved to LV 2025 Q3 and am experiencing some really awkward behaviour.

It seems like this version of LabVIEW is not doing a great job of isolating different contexts of code within the IDE, perhaps specifically for VIMs.

I have a class which contains a vim which allows me to input both child classes (uses only parent methods within) and adapt to a secondary datatype at the input. This has been working fine for years in other LV versions. But int his version, if I have a VI containing an object which uses this vim on both "My Computer" context AND on an FPGA context, the VI is broken. If I remove the dependency from one or other of the contexts, the VI is no longer broken.

This is new for this version of LabVIEW. I have also other observations that the compile cache is having again more of an impact on the code than it should, there somewhere seems to be some utilisation of compiled cache information AHEAD of the actual VI on disk which leads to all kinds of chaos.

If I can, I'll try to get a mock up and running.

[Intaris]

Bumping this for myself.

I have not forgotten.... I'm absolutely inundated with other things to solve, this might take a while to get back to.....

[mcduff]

I don't have an answer to your question, but something profound has recently changed with the compiler. Code complexity has gone way up with a parallel loop, weird issues that can only be solved with clearing the compiled cache, and other issues I cannot recall at the moment.

[Intaris]

I have only one new data point:

My afore-mentioned LVOOP problem.... I can "Solve" it by opening the parent which contains the VIM, hitting the "Apply to all contexts" will actually get the VI working again. But then it breaks ont he other target. It appears it's only runnable on one target at a time.

IF this helps in the handling of the inlined code in the background, I could theoretically get used to the new workflow IF it didn't mean going through potentially dozens of VIs to switch contexts..... This used to be handled automatically by the IDE.

Again, not much further information, but something has clearly changed with respect to the handling of inlined code and having VIs open in multiple contexts.....