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: How does one activate an already registered IS2009 Premier edition ?
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 12, 2008
03:01 PM
How does one activate an already registered IS2009 Premier edition ?
IS2009 Premier is already installed and IsCmdBld.exe builds my projects successfully. isDev.exe crashes upon invocation. Maybe because the PC is behind a firewall and cannot go outbound to the internet. Not sure, but , I did get a good setup.exe built. However, upon launch of my product setup.exe, I get a pop-up msg:
"This Setup was created with an EVALUATION VERSION of InstallShield".
Now I guess I need to activate this already registered IS2009 version ?
How? ... and is the isDev.exe crash going to kill the activation process ?
"This Setup was created with an EVALUATION VERSION of InstallShield".
Now I guess I need to activate this already registered IS2009 version ?
How? ... and is the isDev.exe crash going to kill the activation process ?
(4) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 12, 2008
04:26 PM
You only need to register once, but you need to activate every time you install/reinstall. I believe it's in the Help About you'll see a button for "buy it now" or similar.
It'll start up a wizard that if it can't connect to the activation servers will generate an xml message to email to acresso. When you get the response you enter it and your activated.
Also since your running Premiere, you shouldn't be building with IS. You should just be using the Stand Alone Build. The SAB inputs the key during the install but otherwise doesn't require activation. You can download the SAB by doing a "Check for product updates" in the IS IDE.
It'll start up a wizard that if it can't connect to the activation servers will generate an xml message to email to acresso. When you get the response you enter it and your activated.
Also since your running Premiere, you shouldn't be building with IS. You should just be using the Stand Alone Build. The SAB inputs the key during the install but otherwise doesn't require activation. You can download the SAB by doing a "Check for product updates" in the IS IDE.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 13, 2008
11:02 AM
thanks for the tips. I had the build admin try SAB initially and gave up to go to the full install, IS, since SAB was getting MergeModule errors (product is pulling in VC90 runtime merge module object support within its setup.exe).
Could at this point (since IS is building fine and incorporating MergeModule support) I have the build admin simply copy all files from IS to SAB from subdirectories like Modules, ObjectGallery, Objects, ObjectsPro, Redist ??
(can you tell I'm getting desperate ?)
Could at this point (since IS is building fine and incorporating MergeModule support) I have the build admin simply copy all files from IS to SAB from subdirectories like Modules, ObjectGallery, Objects, ObjectsPro, Redist ??
(can you tell I'm getting desperate ?)
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 13, 2008
11:27 AM
Yes, if you pull some dependency into your development environment, it also has to exist in the build environment.
What I typically do is wire the dependency into the project using a Path Variable that makes it relative to the IS Project Location and then check the dependency into source control. This way when I pull the source tree down and find it, it should all work without having to us a `prime the pump` pattern on the build box.
What I typically do is wire the dependency into the project using a Path Variable that makes it relative to the IS Project Location and then check the dependency into source control. This way when I pull the source tree down and find it, it should all work without having to us a `prime the pump` pattern on the build box.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 13, 2008
11:41 AM
ThX again for the tip.. I've done source area dependency technique (pointing to source build tree) for other installers/situations... it is the way to go, when you can. Ah, just checking out "-o "... I'll have to play with this using SAB. Maybe the solution is within reach now (getting past the SAB MergeModule error which made me seek IS solution). I appreciate the explanation and extra insight as well.
