VI Analyzer always flags VI version in LabVIEW 2011 f2

[shew82]

It seems to me that whenever I run VI analyzer on VIs saved in LabVIEW 2011 f2 (11.0f2) I get a "VI Saved Version" warning along the lines of:

"Your current version of LabVIEW is 11.0f2, but this VI is saved in version 11.0.  Consider mass compiling your VIs so they are all saved in the current version of LabVIEW."

I would go and try and make a little patch (For my systems at least) but the test VI is password protected...

Is it just me, and if not, any chance of a fix?

Thanks,

Shaun

[altenbach]

I am not aware of any f2 revision of LabVIEW 2011. Where did you get it?

Have you tried masscompiling as suggested? A VI can be masscompiled even if it is password protected.

[Matthew_Kelton]

It's been out a while now.

http://digital.ni.com/public.nsf/allkb/6BEF4B41E21B828C862578FC0066DF5C

[shew82]

unfortunately mass compiling makes no difference. I suspect its because the VI version tag is still stored as 11.0 even though the LabVIEW version tag is 11.0f2

[altenbach]

---

@Matthew Kelton wrote:

It's been out a while now.

---

Hmmm, I don't have it and NI update service says I am up to date.... go figure. I'll look into it.

[JÞB]

I just pulled it from the download site.  "Available from Update Service: NO"

[Darren]

I already had CAR# 302244 for a similar issue.  Can you try the attached test LLB (password removed, as the test doesn't have any private functionality in it) and see if it properly addresses the issue?  Backup your copy in [LabVIEW]\project\_VI Analyzer\_tests\General\File Properties, replace it with this one, and let me know how it goes.

[shew82 · Accepted solution]

That *almost* fixed it...

If you switch out the "Search/Slit String" function for a "Match Pattern" function, it works like a charm... see attached modified LLB.

[Darren]

---

@shew82 wrote:

If you switch out the "Search/Slit String" function for a "Match Pattern" function, it works like a charm...

---

Ah, good call. I made a swift edit to the test before passing it on, not noticing that those were Search/Split Strings and not Match Pattern.

Ok, if, with the Match Pattern edit, the test works properly for you, I'll go ahead and put it in to the 2012 branch.  Thanks for testing it!