how to assign a version number after i compiled a DLL in LabVIEW 7?

[brock85]

I'm using LabVIEW 7 Express. After i compiled a DLL i would like to assign a version number to the DLL for tracking purpose. How do i do this?

I could do this in LabVIEW 2012 but i only have LabVIEW 7 Express in current company. Please help.

[Norbert_B]

Instead of giving an answer (as i don't know it) i want to ask you/the company the following:

Which OS are you going to use the next couple of years?

If the answer does not match "Windows XP or older" but something like "Windows 7 or later", you shouldn't create that DLL in the first place.

LV 7.1 supports up to Windows XP, i think that 7.0 supports the same OS versions....

Supported Platforms

LabVIEW supports Windows 2000/NT 4.0 Service Pack 6 or later/XP. LabVIEW does not support Windows Me/98/95.

(From the 7.1 readme)

Norbert

[rolfk]

Just as Norbert already said, LabVIEW 7.0 is really old. It was released somewhere around 2002/2003. So you talk about a software that is at least 10 years old. Lots of changes have happened since, many of them security related. So I think your company should really consider to upgrade soon.

That all said, if you know about Windows API programming you can always call the apropriate WinAPI functions to add a version resource to your executable/dll image. Recent LabVIEW versions have that in the Application Builder included. For old versions it is DIY.

[brock85]

Thank you very much for the help. My company is using LabVIEW 2012 now.

This is just an "ancient" project which is going to end soon and still running in LabVIEW 7 and there is no need to be converted to 2012.

I'm able to change the DLL version number using 3rd party software, just curious why LabVIEW 7 could not do that.

Thank you again.... 🙂 

[rolfk]

---

@brock85 wrote:

I'm able to change the DLL version number using 3rd party software, just curious why LabVIEW 7 could not do that.

Thank you again.... 🙂 

---

Well, LabVIEW is good, but it doesn't put your trash out the door either! 😉

The main reason that LabVIEW did not do it back then is a combination of various things.

LabVIEW being multiplatform and trying to do as much as possible on all supported platforms means that sometimes things do not get implemented at the earliest possible moment if they can't be implemented on all platforms. Also LabVIEW was used happily for over 15 years without this feature. Since LabVIEW builds the application in its own way adding a version resource to the DLL is an after the fact step. One which is still not very common to find tools in even nowadays and much less 10 years ago, when LabVIEW 7.0 was released. the according Windows API to do that used to be not very well documented.