Get Project LabVIEW Version

Lets say I have a random LabVIEW file. I can use the Get File Type.vi found in the VI.lib to figure out what the file type is. It could be an Instrument, Control, Project, Library, XControl or a bunch of others. If it is a VI I can use the Get VI Version invoke node to find what version of LabVIEW it was made with. If it is a Library I can use the Library.Get File LabVIEW Version to get the version, or if it is a project I can use the Project.Get File LabVIEW Version.
What I find strange, is if I have a VI saved in 2013, and I run the invoke node for reading the LabVIEW version but my development environment is 2011, it will say the VI was made with 2013. But if I have a project saved in 2013, and use the invoke node to read the version, and my development machine is 2011, I get an error saying File version is later than the current LabVIEW version error 1125.
Is this a bug? I mean I can read the project file as text and parse it with a XML parser to find the version. So why does this function choke and die when trying to read newer file versions, but a VI and Library can be read no problem?
Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously.
Solved!
Go to Solution.

This was a bug in the "Project.Get File LabVIEW Version" method. It was fixed in LabVIEW 2012.
Darren Nattinger, CLA
LabVIEW Artisan and Nugget Penman

Similar Messages

Get project build version

Hi all.
I cannot understand how to get SSIS project build version.
For example.
I created new SSIS project - proj.ispac and set build version = 22, major build version = 33 and minor build vesrion = 44.
I added a package into my project, named it as pack.dtsx and set its build version = 5, major build version = 6 and minor build version = 7.
Now I put 'sctipt task' in my pack.dtsx and I want to know the build version not of my pack.dtsx but of my proj.ispac.
I can get to System::VersionBuild, System::VersionMajor and System::VersionMinor variables from within the script task and they contain versions of the package pack.dtsx (build version = 5, major build version = 6 and minor build version as 7).
But I want to get to the build information of the project proj.ispac (build version = 22, major build version = 33 and minor build version as 44).
I cannot find any clue how to get it.

Hi Denis,
If I remember correctly there is no API to get it.
Arthur My Blog

Programmatically get labview project executable version

Hello,
I would like to programmatically get the executable version number from the build specifications in my LabVIEW project so I can display it on the Title bar in my application.
I looked at the application properties and was able to get to the build specifications property from my project, but I could not find out how to retreive the version number.
Attached are screenshots of the project build specification window with the version number information I want to retreive and VI project example that I did in LV 8.2.1.
Thank you,
Russell
Engineering Team Leader
G Systems, www.gsystems.com
Certified LabVIEW Architect
Certified Professional Instructor
Attachments:
LV project executable version.zip ‏42 KB

A LabVIEW executable doesn't have a project (that's a development tool), but this thread should help you
Ton
Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
Nederlandse LabVIEW user groep www.lvug.nl
My LabVIEW Ideas
LabVIEW, programming like it should be!

Getting error when updating the JavaScript API for Office and manifest schema files in your Visual Studio project from version 1.0 to 1.1

Hi,
I`m getting error message like "None of the apps in your project can be activated in the target. The manifest file of one or more apps contain API sets or Office applications that are not supported by
the target Office client. To debug those apps, update manifest files to exclude any unsupported API sets or Office applications, and then start the project again. Alternatively, you can debug your apps by using Office 365 as a target." when when
updating the JavaScript API for Office and manifest schema files in your Visual Studio project from version 1.0 to 1.1 in manifest file though i have added host elements.
any help in this regard is highly appreciated
Thanks,
Santosh Sutar

Hi Satosh Sutar,
Based on the description, you got the error message when you update the apps from version 1.0 to 1.1.
From the error message, it seems the menifest include some settings no allowed in the new version. Would you mind sharing more detail about how you update the project?
And here is an article about updating apps for Office and menifest schema files in the project for your reference:
How to: Update the JavaScript API for Office and manifest schema files in your Visual Studio project from version 1.0 to 1.1
Regards & Fei
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Where can I get a trial version of LabView for Unix

I'm using a Solaris v2.61 at work and I'm trying to gain remote accsesss to a TDS 3032 Tektronix o-scope. Where can I get a trial version of LabView for Unix?

At least for LV 7.
You may get NI to give you a LV 6 version for Solaris or Linux. Send an e-mail to sales and see what they say.
http://sine.ni.com/apps/we/nicc.call_me?p_action=country&p_lang_id=US
2006 Ultimate LabVIEW G-eek.

I'm trying to read some XML data from temperature logger over my network. I'm using LabView version 2009 sp1. I'm using the URL Get Document Vi. It works fine when using Internet sites like google or foxnews etc...

I'm trying to read some XML data from temperature logger over my network. I'm using LabView version 2009 sp1. I'm using the URL Get Document Vi. It works fine when using Internet sites like google or foxnews etc...
When I use it with my temperature logger most of the time I get an Error 66...but some times it does work and actually retrieves the document.
I can use the same address "http://172.22.21.68/XMLfeed.rb" (Internet Explorer or Google Chrome) in my browser and get a response every time. When accessing from my browser the server in the temperature logger does take around 6 seconds to respond, but it does respond every time.
Is the URL Get Document Vi exceeding a timeout? If so, where can I set it to wait longer?
Attachments:
Error 66.jpg ‏183 KB

It looks like the TCP Buffered Read has a 2.5 sec timeout, I believe that is where I had trouble as well. Try creating your own URL Get HTTP Doc vi in which you call URL Get Document in normal mode, with an appropriate number of characters to fetch (enough characters so that you capture all the important data in the XML file).
Attachments:
ex1.PNG ‏33 KB

Poll: Which LabVIEW version do you use for new projects?

I have posted a poll on the LAVA forums, here:
Poll: Which LabVIEW version do you use for new projects?
Thank you for taking the time to tell us your thoughts.

I'm giving this thread a bump to remind eveyone that we want to know your opinion. Please vote in our poll.
Thanks,

What are developers' opinions on how best to handle upgrading large code libraries with multiple apps to new a labview version?

I have a large set of code that I've painstakingly migrated from one labview version to another over the years. I have lots of deployed applications that I need to continue to support. From experience and interaction with other developers, I don't think I can continue to migrate every application to a new labview version when I upgrade going forward. Every application seems to break in one way or another, the builds don't work right and need to be re-done, and its too much time to get all my applications working and tested again. That opinion is solidified by NI's policies that make it impossible to install old toolkit versions on new labview versions, for example. Compatibility is often being sacrificed so NI can develop labview in the direction they choose. So I have to take the position that whatever version I write an application in will probably need to be maintained in that labview version throughout it's life.
In light of this, how are other developers managing older applicatiosn written in older versions of labview. Right now I have a virtual PC on my system with 7.1, 8.0, 8.2, and 8.5 all running on different virtual PC's so I can keep each installation separate. I strongly recommend this approach. But keeping my large libraries of code separate is tough. They are many GB, they all link to each other, and I always get worried even when I separate them in different directories that somehow labview will search in the wrong place and find the wrong version of a sub-vi. Are other people also trying to maintain separate copies of all their code in different labview versions? How are other people managing this problem?
-Devin
I got 99 problems but 8.6 ain't one.
Solved!
Go to Solution.

Hi,
The following directory hierarchy, coupled with a "hierarchical" VI naming strategy, have been effective (for me) at preventing "cross-linking" across projects and LV versions. The storage hierarchy was designed for use within an SCC environment, but works fine independently. Hierarchical-naming insures unique names for application-specific files. Use of Project Libraries (in LabVIEW 8.x) addresses the problem of having different VIs with the same name, still, it gives me warm-fuzzies to have app-specific files named uniquely, and I can't imagine not using Hierarchical-naming anymore - it's described at-length in section 2.1 of attached .doc..
Note: It's been my experience that companies identify resources as supporting specific "Programs", where a Program is related to a product or "family" of products, so, under <Programs> (below) each "Program" subdirectory encapsulates product-specific (or product-family-specific) applications. Also, assuming no SCC tool is being employed the <Production> directory (below) exists as a repository for distributables. All distributables required to reproduce a test-station should be located under <Production>.
<Software_Root>
<Development>
| <Common>
| | <LabVIEW_61>
| | | <Drivers>
| | | | <DMM>
| | | | <OS>
| | | | <PS>
| | | <Utilities>
| | | <File>
| | | <Error>
| | | <String>
| | <LabVIEW_711>
| | <LabVIEW_82>
| | <LabVIEW_851>
<Programs>
* Program-specific applications that (probably) have distributables
| <Program_#1>
| | <Application_#1>
| | <Docs>
| | <Source>
*       Individual, application-specific, VIs go here
| | <Application_#2>
| | <Application_#3>
| <Program_2>
| | <Program_3>
| <Tools>
* Tools are NOT "program"-specific, and, may have distributables
| <SomeTool>
| <SomeOtherTool>
<Production>
| <COTS&Freeware>
| <Programs>
| | <Program_1>
| | | <Application_#1>
| | | | <Application_#1_Rev#1>
| | | | Application_#1.bld>
| | | | <EXE>
| | | | <Installer>
| | | | <Source>
| | | |    Application_#1.llb>
*           Distributable is created from LLB "snapshot", not directly from development tree
| | | <Application_#2>
| | | | <Application_#2_Rev#1>
| | | | Application_#2.lvproj>
| | | | <EXE>
| | | | <Installer>
| | | | <Source>
| | | |    Application_#2.llb>
| <Tools>
"Inside every large program is a small program struggling to get out." (attributed to Tony Hoare)
Attachments:
StyleGuide.doc ‏941 KB

How do I get project downloaded to 2nd user's PC?

I'm testing RH6 with RoboSource Control 3. Was able
to covert existing project and get it up onto server as single
user. Checking in out as single user is fine. Now, I want to test
how it works with 2nd user.
When 2nd user tries to get project off the server, it seems
to be okay. Used "recursive" to get the file structure.
When she opens the project in RH6, gets error that cpd file
is corrupt. Delete the cpd and try again, same error.
If ignore the error message, the project opens but there are
lots of broken links. Also, the single source info for the project
is missing (should be FlashHelp).
How do I get this to work for 2nd user? I'm not an IT person,
just a tech writer, so need step by step instructions.

Once you've got the RSC DB set up, loading the project into
source control is easy. First, you'll need to get RH acquainted
with the new DB. To do this, use RSC3 Explorer to open the new
database. Once you've created a connection to the new DB, you can
close the RSC Explorer. Then open your project in RH6 and click the
Add to Version Control button in the RoboHelp toolbar. Select the
correct connection name; other than that, accept the defaults. (For
the Root Path box, you'll probably need to click the "..." button
and then select the top level folder, $.) Wait for the process to
complete. When it's done, all the files will be checked out to you.
Go ahead and check them all back in.
As for the 2nd user, I like to skip some of the setup work by
doing it this way: zip the folder containing the source files and
let the other users extract it onto their machines. They can just
open the project from the xpj, and the setup is largely done for
them already. And for large projects, the cpd file is already
built, which can save time.
I'm new at RSC3, and I'm working from memory here, so there
may be details missing. Still, that's the general gist.
HTH,
G

How to hide the file name (the bizarre number assigned by the camera) when exporting an image version in aperture from an album. Pl understand I want to keep the file name in the project library version.

how to hide the file name (the bizarre number assigned by the camera) when exporting an image version in aperture from an album. Pl understand I want to keep the file name in the project library version.

Within Aperture you have Images, which are constructed on-the-fly from two files (the Master and the Version). You get an image-format file _only_ when you export an Image. You select the file name (usually a scheme) when you create an image-format file (that is, when you export). Look under "Aperture→Presets→File Naming" for built-in Presets. You can, of course, create your own or customize any provided.
The Preset is applied to only the file newly created by your "export" command. It is not applied to the Image in Aperture (unless you rename your Versions or your Masters).

How to get the latest version from DTR

Hi all,
I have all the latest code in my system 1 and i checkined the activites.Now i want all that code in my system 2.
Now i used sync from sources to get the lateset code.
But i am not able to get all the files and the build is getting failed.
Can any one plz help me out
Regards
Padma N

Hi,
Inorder to get the lateset version from DTR i used the procedure given by you.But at the second time if i want to get the lateset version from DTR wat to do??I didnt find the option of create project again because i already have to project in my workspace.
wat to do inorder to get the lateset source code from DTR 2nd time???
Regards
Padma N

Sypris Teslameter Driver_too early to convert to 8.5 labview version

I am new to labview (8.5) programme and trying to use it to run my setup. I connected the Gaussmeter/Teslameter (FW Bell Sypris 6010) to the computer using serial port and RS-232 cable and used the driver (from the company) for this type of devices in order to allow labview to communicate with this device but there is always an error when I try to access the device through labview. This error says:
"VI version is too early to convert the current LabView version"
I would really appreciate any help in getting this solved.
Many thanks
Hadiq
Islam means peace
Solved!
Go to Solution.
Attachments:
FWB6010.zip ‏412 KB

Thanks for your suggestion. I did it and hope to get it sorted.
Many thanks,
hadiq
Islam means peace

How can get an earlier version of my LDM ???

Hi,
we come to one issue:
say we modify LDM at Nov 1th, and modify LDM at Nov 2th,but after commit what we did at Nov1th,and Nov 2th, we find there are 'mistakes' in Nov 2th,
how can we get an earlier version of LDM?(in our case, we want revert to version Nov 1th).
we use SDDM Version 3.1.1.703,and we share the project under subversion managed.
more questions:
(under subversion managed SDDM projet)
1.what is best praise of backup in case we do something wrong and want rollback whole change to previous version?
2.how to do that ,is there any document guide ?(I searched this forum, seems not find similar topic)
Thanks,
Jinbo

Thanks Philip,
now we can see the old reversion.
but new issue comes.
say two users:user1 & user2 are working on the LDM, and remote directory called LDM_remoate
at Nov 2th,
user1 have a latest local working copy under his machine directory LDM_local_user1
user2 have a latest local working copy under his machine directory LDM_local_user2
At Nov3th,
user2 found some mistakes when user1 checked in at Nov 1th,so user2 want to get a earlier version say Nov 1 th,
according to your guide, user2 get the design reversion number Nov 1th, and re check out at new working copy(Nov 1th) under new local directory:LDM_local_user2_new
when user2 open LDM_local_user2_new, it indeed come back to version Nov 1th,
but in the incoming change window, it still show many incoming changes,
how to make the remote LDM_remote to become like LDM_local_user2_new? so that user1 only need check incoming change from LDM_remote as usual to make at local copy
LDM_local_user1 also reverted to version Nov 1th?
hope I make it clear to you.
thanks,
Jinbo

How can I programatically get the TestStand version?

I want to programatically get my Teststand version. Can I get this from inside a LabVIEW VI? I'm writing a VI that produces a Software Description Document and one of the things I want in there is my TestStand version.

You can use the Engine.Version to get a string of the version number. This is useful for a string for display information.
For more detailed information, you can use the following properties:
Engine.MajorVersion
Engine.MinorVersion
Engine.RevisionVersion
Allen P.
NI

How do i get the trial version from text off my movie

how do i get the trial version from text off my movie

billwwww
What version of Premiere Elements is involved and on what computer operating system is it running?
Do you now have a purchased version of Premiere Elements?
You can not remove the Adobe watermark from an export from the tryout, be it an export of a file saved to the computer hard drive
or a burn to disc product.
But, you can remove the Adobe watermark from a project file (.prel) from the tryout. To do that, you open the project file from the tryout
in the purchased version. Then there are two possible scenarios
1. You go to Timeline Menu/Delete Rendered Files - the Adobe watermark is gone
or
2. You do nothing after you open the tryout project file in the purchased Premiere Elements. Many of us, including myself, have found
that opening the tryout project in the purchased program causes the watermark to disappear spontaneously.
Please let us know which works for you.
Thank you.
ATR

Get Project LabVIEW Version

Similar Messages

Maybe you are looking for