This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: InstallShield 2018 SP1 upgrade
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page

Not applicable
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 16, 2018
01:20 PM
InstallShield 2018 SP1 upgrade
I just upgraded IS2018 Premier Edition to Service Pack 1 (I was pointed by the Software Manager) and now all projects need upgrade.
On my build server I have a IS Standalone 2018 installed.
Will my projects (saved converted by IS 2018 SP1) will still build with the same ISSA 2018?
If not, how do I revert to IS 2018?
Thanks,
On my build server I have a IS Standalone 2018 installed.
Will my projects (saved converted by IS 2018 SP1) will still build with the same ISSA 2018?
If not, how do I revert to IS 2018?
Thanks,
(4) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 16, 2018
01:44 PM
If project files are upgraded, then when you opened the project files it would have created a backup of the original version. it will look something like this PROJECTNAME.### where ### represents the original version.
If the project file did not require an upgrade then the renamed file will not be present.
Me, I would just use source control (svn, git, Hg, etc) and revert my changes.
Someone else will need to address the issue of the Standalone build compiling builds. I did find something interesting in my build system. A few days ago I realized that I have a project that is still compiling on the standalone build machine that uses IS2016 Standalone build. However, the project file was never converted and is still IS2015. So the Standalone Build has some ability to compile project files from previous versions - I don't know about newer versions though.
If the project file did not require an upgrade then the renamed file will not be present.
Me, I would just use source control (svn, git, Hg, etc) and revert my changes.
Someone else will need to address the issue of the Standalone build compiling builds. I did find something interesting in my build system. A few days ago I realized that I have a project that is still compiling on the standalone build machine that uses IS2016 Standalone build. However, the project file was never converted and is still IS2015. So the Standalone Build has some ability to compile project files from previous versions - I don't know about newer versions though.

Not applicable
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 16, 2018
01:55 PM
DLee65 wrote:
If project files are upgraded, then when you opened the project files it would have created a backup of the original version. it will look something like this PROJECTNAME.### where ### represents the original version.
I know that and I have no problem using the backed up files.
But the problem is:
On my development machine I have IS 2018 SP1, so any project will be converted.
On my build server I have a ISSA 2018.
Will ISSA 2018 able to work with the converted projects?
Is NO, I need to synch the 2 versions, but:
- How to revert on my machine from 2018 SP! to 2018?
- How to get a ISSA 2018 SP1 for build server
Thanks,
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 17, 2018
07:38 AM
Hi loanb22,
Answering to your queries:
- How to revert on my machine from 2018 SP! to 2018?
- How to get a ISSAB 2018 SP1 for build server
Hence SAB builds don't have software update support,your build server won't get updates.You can go with later one i.e make build server known to InstallShield SAB 2018 SP1.You can download InstallShield SAB SP1 build from your PLC account.
Thanks,
Jenifer
Answering to your queries:
- How to revert on my machine from 2018 SP! to 2018?
- How to get a ISSAB 2018 SP1 for build server
Hence SAB builds don't have software update support,your build server won't get updates.You can go with later one i.e make build server known to InstallShield SAB 2018 SP1.You can download InstallShield SAB SP1 build from your PLC account.
Thanks,
Jenifer
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 19, 2018
04:41 AM
Hi,
-To address your first issue,you may need to attach log file from Flextnet connect folder to get more insight
-This issue may be specific to UI theme,which needs to be fixed from InstallShield side.You may expect this to be fixed in their upcoming releases
-About third one,Symantec flagging with softwares had become trivial now-a-days.It depends upon the type of quarantine that you are flagged.If it is on installshield's setup.exe/binaries you can submit those to them. prepaidgiftbalance
Last week i was been flagged for .log file,dint even have clue about it.
Thanks,
-To address your first issue,you may need to attach log file from Flextnet connect folder to get more insight
-This issue may be specific to UI theme,which needs to be fixed from InstallShield side.You may expect this to be fixed in their upcoming releases
-About third one,Symantec flagging with softwares had become trivial now-a-days.It depends upon the type of quarantine that you are flagged.If it is on installshield's setup.exe/binaries you can submit those to them. prepaidgiftbalance
Last week i was been flagged for .log file,dint even have clue about it.
Thanks,
