Nov 28, 2018
02:18 AM
How to convert .ism from IS 2013 to IS 2016 using console? Other information - 1) License type is - InstallShield 2016 Standalone Build Concurrent License Perpetual. (The IS is without UI interface) 2) Command to build the project is - "C:\Program Files (x86)\MSBuild\12.0\Bin\MSBUILD.exe"?? MyFile.isproj Is there any document for .ism XML file tags and their meaning that can help me convert .ism to IS 2016
... View more
Nov 21, 2018
09:50 AM
Tried following - Case A ----------------------------------- Type of file: InstallShield MSBuild Project File (.isproj) - + Type of file: ISM File (.ism) // created originally using old IS 2013 with tag 774 >SchemaVersion774 Run Build command: "C:\Program Files (x86)\MSBuild\12.0\Bin\MSBUILD.exe"?? MySetup.isproj Result: Successfully build .msi file. Problem - On final .msi file, right click - Properties - Details - "Program name: InstallShield 2013" Expected - On final .msi file, right click - Properties - Details - "Program name: InstallShield 2016" ____________________________________________ Tried following - Case B ----------------------------------- Type of file: InstallShield MSBuild Project File (.isproj) - + Type of file: ISM File (.ism) // created originally using old IS 2013 - >SchemaVersion774 + >SchemaVersion777 Run Build command: "C:\Program Files (x86)\MSBuild\12.0\Bin\MSBUILD.exe"?? MySetup.isproj Result: .msi file was not created as it failed. Manually changing 774 to 777 in .ism caused it to failed. ____________________________________________ So, may be there is a way to upgrade .ism from IS 2013 to IS 2016 that can help
... View more
Nov 20, 2018
11:50 PM
Hello, The IS project was created using IS 2013. Please guide, how to upgrade project and final .msi details to version 2016. Other information - 1) License type is - InstallShield 2016 Standalone Build Concurrent License Perpetual. (The IS is without UI interface) 2) Command to build the project is - "C:\Program Files (x86)\MSBuild\12.0\Bin\MSBUILD.exe"?? MyFile.isproj Observations / tries - 1) .isproj - - .isproj file manually update to use IS 2016 - + Problem - On final .msi file, right click - Properties - Details - "Program name: InstallShield 2013" Expected result : "Program name: InstallShield 2016" (que) How to make details "Program name: InstallShield 2016" ? (2) .ism - .ism file has SchemaVersion 774 (indication IS 2013). It is not 777 (which is for IS 2016). (que) What is difference between SchemaVersion and InstallShield version ? (que) Should SchemaVersion be changed to 777 manually in ism file ? Thank you
... View more
Labels
- Labels:
-
InstallShield 2016
Latest posts by vikas_chablani
Subject | Views | Posted |
---|---|---|
1756 | Nov 28, 2018 02:18 AM | |
1756 | Nov 21, 2018 09:50 AM | |
1925 | Nov 20, 2018 11:50 PM |
Activity Feed
- Posted Understanding .ISM XML file of IS 2013 vs IS 2016 on InstallShield Forum. Nov 28, 2018 02:18 AM
- Posted Additional information on InstallShield Forum. Nov 21, 2018 09:50 AM
- Posted Upgrade project ism and isproj - console IS 2016 Standalone Build Concurrent w/o UI on InstallShield Forum. Nov 20, 2018 11:50 PM
- Tagged Upgrade project ism and isproj - console IS 2016 Standalone Build Concurrent w/o UI on InstallShield Forum. Nov 20, 2018 11:50 PM
- Tagged Upgrade project ism and isproj - console IS 2016 Standalone Build Concurrent w/o UI on InstallShield Forum. Nov 20, 2018 11:50 PM
- Tagged Upgrade project ism and isproj - console IS 2016 Standalone Build Concurrent w/o UI on InstallShield Forum. Nov 20, 2018 11:50 PM
- Tagged Upgrade project ism and isproj - console IS 2016 Standalone Build Concurrent w/o UI on InstallShield Forum. Nov 20, 2018 11:50 PM
- Tagged Upgrade project ism and isproj - console IS 2016 Standalone Build Concurrent w/o UI on InstallShield Forum. Nov 20, 2018 11:50 PM