vc6
30th June 2008 17:51 UTC

Ver_major, Ver_minor, Ver_revision, Ver_build ...
  VER_MAJOR, VER_MINOR, VER_REVISION, VER_BUILD - where do I define them?


Are these supposed to be hard coded into my NSIS script? For example:

!define VER_MAJOR "1"

>!define VER_MINOR "4"

>!define VER_REVISION "3"

>!define VER_BUILD "4" 

Or, should these be programmatically extracted from the software installed?

If the latter, is there an API/plugin in NSIS that extracts version info from Windows programs?

Also, I noticed that the makensis.nsi example saves VER_MAJOR, VER_MINOR, VER_REVISION, VER_BUILD to the registry. What is the purpose of that?

Thanks.

Anders
30th June 2008 18:36 UTC

for a guy named vc6, you don't really seem that hardcore, anyway, try GetDLLVersion

vc6
30th June 2008 19:03 UTC

Originally posted by Anders
for a guy named vc6, you don't really seem that hardcore, anyway, try GetDLLVersion

Thanks for the pointer to GetDLLVersion, I didn't know about it.

As for being hardcore, you're right - I am not hardcore at all. :)

Any insight as to why makensis.nsi example saves VER_MAJOR, VER_MINOR, VER_REVISION, VER_BUILD to the registry?

Thanks!

Red Wine
30th June 2008 19:26 UTC

Any insight as to why makensis.nsi example saves VER_MAJOR, VER_MINOR, VER_REVISION, VER_BUILD to the registry?

How about wants to know the installed version?

vc6
30th June 2008 19:47 UTC

Originally posted by Red Wine
How about wants to know the installed version?

You mean comparing between what's already installed and the one to be installed?

So that it can prevent the user from installing an older version?

Thanks!

Red Wine
30th June 2008 19:55 UTC

I mean that would be rather explanatory if you try it your self. It wouldn't harm neither you or your machine.
makensis.nsi is the actual script which builds nsis installer.