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: What's with the naming - "2012 Spring"?
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
‎May 10, 2012
10:41 AM
What's with the naming - "2012 Spring"?
It's been nearly a year since InstallShield 2012, and now we get a new version of 2012 named 2012 Spring. When I first saw the email announcing this, I literally thought it was some kind of training seminar or something. And almost deleted it. Just before I deleted it something caught my eye, so luckily I didn't.
Then I came back here after a while being away from the forums, and sure enough it was listed as a separate version from 2012.
I didn't even think that this was, in effect, InstallShield 2013. What's the motivation behind this confusing naming convention. Not to question marketing, but this is kinda confusing.
Then I came back here after a while being away from the forums, and sure enough it was listed as a separate version from 2012.
I didn't even think that this was, in effect, InstallShield 2013. What's the motivation behind this confusing naming convention. Not to question marketing, but this is kinda confusing.
(2) Replies
‎May 21, 2012
12:34 PM
I agree with the name confusion. It makes it difficult to decide when it is worth the effort to upgrade my install projects to a newer version of InstallShield. When is the next release of InstallShield planned? Is there going to be an InstallShield 2013? What is the frequency of InstallShield releases planned?
I go through considerable testing to consider a version of InstallShield stable enough to upgrade and it takes time to change my different product templates to support a new version. Since Flexera does not support downgrade rights it makes this situation even worse. I do not want to be forced to upgrade to a new InstallShield version if it does not give me any new functionality that I require.
I go through considerable testing to consider a version of InstallShield stable enough to upgrade and it takes time to change my different product templates to support a new version. Since Flexera does not support downgrade rights it makes this situation even worse. I do not want to be forced to upgrade to a new InstallShield version if it does not give me any new functionality that I require.