NSIS - put EXE version into name of installer

前端 未结 7 717
臣服心动
臣服心动 2020-12-24 03:04

NSIS has a Name variable that you define in the script:

Name \"MyApp\"

It defines the name of the installer, that gets displayed as the win

相关标签:
7条回答
  • 2020-12-24 03:38

    Since NSISv3.0 this can be done with !getddlversion without using any third-party software:

    !getdllversion "MyApp.exe" ver
    Name "MyName ${ver1}.${ver2}.${ver3}.${ver4}"
    OutFile "my_name_install_v.${ver1}.${ver2}.${ver3}.${ver4}.exe"
    
    0 讨论(0)
  • 2020-12-24 03:41

    There might be a very simple way to do this, but I don't know what it is. When I first started using NSIS, I developed this workaround to suit my needs and haven't revisited the problem since to see if there's anything more elegant.

    I wanted my installers to have the same version number, description, and copyright info as my main executable. So I wrote a short C# application called GetAssemblyInfoForNSIS that pulls that file info from an executable and writes it into a .nsh file that my installers include.

    Here is the C# app:

    using System;
    using System.Collections.Generic;
    using System.Text;
    
    namespace GetAssemblyInfoForNSIS {
        class Program {
            /// <summary>
            /// This program is used at compile-time by the NSIS Install Scripts.
            /// It copies the file properties of an assembly and writes that info a
            /// header file that the scripts use to make the installer match the program
            /// </summary>
            static void Main(string[] args) {
                try {
                    String inputFile = args[0];
                    String outputFile = args[1];
                    System.Diagnostics.FileVersionInfo fileInfo = System.Diagnostics.FileVersionInfo.GetVersionInfo(inputFile);
                    using (System.IO.TextWriter writer = new System.IO.StreamWriter(outputFile, false, Encoding.Default)) {
                        writer.WriteLine("!define VERSION \"" + fileInfo.ProductVersion + "\"");
                        writer.WriteLine("!define DESCRIPTION \"" + fileInfo.FileDescription + "\"");
                        writer.WriteLine("!define COPYRIGHT \"" + fileInfo.LegalCopyright + "\"");
                        writer.Close();
                    }
                } catch (Exception e) {
                    Console.WriteLine(e.Message + "\n\n");
                    Console.WriteLine("Usage: GetAssemblyInfoForNSIS.exe MyApp.exe MyAppVersionInfo.nsh\n");
                }
            }
        }
    }
    

    So if you use that application like so:

    GetAssemblyInfoForNSIS.exe MyApp.exe MyAppVersionInfo.nsh

    You would get a file named MyAppVersionInfo.nsh that looks something like this (assuming this info is in your executable):

    !define VERSION "2.0" 
    !define DESCRIPTION "My awesome application"
    !define COPYRIGHT "Copyright © Me 2010"
    

    At the top of my NSIS script, I do something like this:

    !define GetAssemblyInfoForNSIS "C:\MyPath\GetAssemblyInfoForNSIS.exe"
    !define PrimaryAssembly "C:\MyPath\MyApp.exe"
    !define VersionHeader "C:\MyPath\MyAppVersionInfo.nsh"
    !system '"${GetAssemblyInfoForNSIS}" "${PrimaryAssembly}" "${VersionHeader}"'
    !include /NONFATAL "${VersionHeader}"
    
    !ifdef VERSION
        Name "My App ${VERSION}"
    !else
        Name "My App"
    !endif
    
    !ifdef DESCRIPTION
        VIAddVersionKey FileDescription "${DESCRIPTION}"
    !endif
    
    !ifdef COPYRIGHT
        VIAddVersionKey LegalCopyright "${COPYRIGHT}"
    !endif
    

    The first 3 defines set up the file names to use in the !system call to GetAssemblyInfoForNSIS.exe. This system call takes place during your installer's compilation and generates the .nsh file right before you include it. I use the /NONFATAL switch so that my installer doesn't fail completely if an error occurs in generating the include file.

    0 讨论(0)
  • 2020-12-24 03:45

    I found a way to do this on the NSIS wiki:

    http://nsis.sourceforge.net/Version_Info_manipulations_on_compile-time

    0 讨论(0)
  • 2020-12-24 03:45

    Since NSIS v3.0a0 you can do it directly in the script, no external tools needed: !getdllversion

    Sample code (from the documentation):

    !getdllversion "$%WINDIR%\Explorer.exe" Expv_
    !echo "Explorer.exe version is ${Expv_1}.${Expv_2}.${Expv_3}.${Expv_4}"
    
    0 讨论(0)
  • 2020-12-24 03:48

    You can achieve this using MSBuild.

    1. Just add your .nsi script to project and set this file property Copy to Output Directory value Copy always or Copy if newer.

    2. Add to your project file (e.g. .csproj or .vbproj) following code (suppose your nsi script has name installer.nsi)

      <Target Name="AfterBuild" Condition=" '$(Configuration)' == 'Release'">
        <!-- Getting assembly information -->
        <GetAssemblyIdentity AssemblyFiles="$(TargetPath)">
          <Output TaskParameter="Assemblies" ItemName="myAssemblyInfo"/>
        </GetAssemblyIdentity>
        <!-- Compile NSIS installer script to get installer file -->
        <Exec Command='"%programfiles(x86)%\nsis\makensis.exe" /DVersion=%(myAssemblyInfo.Version) "$(TargetDir)installer.nsi"'>
          <!-- Just to show output from nsis to VS Output -->
          <Output TaskParameter="ConsoleOutput" PropertyName="OutputOfExec" />
        </Exec>
      </Target>
      
    3. Use $Version variable in your nsi script:

      # define installer name
      OutFile "MyApp-${Version}.exe"
      
    0 讨论(0)
  • 2020-12-24 04:03

    Call simple VBS script after NSIS compile:

    Set ddr = CreateObject("Scripting.FileSystemObject")
    Version = ddr.GetFileVersion( "..\path_to_version.exe" )
    ddr.MoveFile "OutputSetup.exe", "OutputSetup_" & Version & ".exe"
    
    0 讨论(0)
提交回复
热议问题