rguggisberg wrote: What type if InstallShield projects? InstallScriptMSI, Basic MSI, Suite? To be honest, I'm not sure. I have just added a 'InstallShield Limited Edition Project' project to the Visual Studio 2015 solution. And when building a 'SingleImage' build, the output is a 'setup.exe' file. I'm adding a screen shot from the General Information view. Can you see from here what kind of InstallShield project? If not, how can I find out what kind of InstallShield project this is? ... View more

rguggisberg wrote: What type of project(s)? C# WPF desktop application, using .NET version 4.6.1. ... View more

rguggisberg wrote: I suppose there a lots of ways to do it depending on your build environment. How are you changing your Assembly Info file? What I do in a TFS environment for InstallScript MSI projects and Suite projects is have TFS set the build number automatically in the build definition. Pass that x.y.BuildNumber.0 as a parameter to a prebuild script which uses TF.EXE to do checkin/checkout programatically. Have that script change any files that need to be changed. 1. For CommonAssemblyInfo .cs & .vb files Checkout file/Change version/Checkin file 2. For each ISM file: Checkout file/Change version/Checkin file (Search for and change the line that contains the string " ProductVersion"). Probably different for Basic MSI project. 3. For .ISSUITE file: Checkout file/Change version/Checkin file ( Search for and change the line that contains the string " ") The version number is changed in the source so if you do manual builds it is still at that version (advantage or disadvantage... depending on your perspective). It is not a simple matter but it can be done. I apologize for not getting back to you earlier. My environment is very basic. I use the extension Automatic Versions to automatically increment version number attributes in AssemblyInfo.cs when building the main project. And I set the same version number to AssemblyVersion and AssemblyFileVersion attributes. I don't build the InstallShield setup project unless I want to build the installer. What I'd like is if it's possible to set a pre-build script or something on the setup project, that copies the version number from AssemblyInfo.cs and sets to the setup configuration prior to building the installer. ... View more