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: GUIDs problem, please help!
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
‎Jan 15, 2009
03:29 AM
GUIDs problem, please help!
Hi guys!
In the past I've written some setup projects customized for each customer. Every project include their specific files, attribute and so on.
Now, we find a way for use a single setup project for every our customer. But there is a problem: every old project has its own new GUID, so if I create this new setup project I suppose that when I will try to install it on a customer PC (that has an old project already installed) it could create problems!
So, since I know all the old GUIDs, can I create a sort of my "black list" in the new project in order to abort the new setup if I detect this old GUIDs?
If yes, what is the IS code for do this?
Other solutions are appreciated...
Thank you!
In the past I've written some setup projects customized for each customer. Every project include their specific files, attribute and so on.
Now, we find a way for use a single setup project for every our customer. But there is a problem: every old project has its own new GUID, so if I create this new setup project I suppose that when I will try to install it on a customer PC (that has an old project already installed) it could create problems!
So, since I know all the old GUIDs, can I create a sort of my "black list" in the new project in order to abort the new setup if I detect this old GUIDs?
If yes, what is the IS code for do this?
Other solutions are appreciated...
Thank you!
(4) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 27, 2009
08:14 AM
Are you using a basic msi project or installscript?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 27, 2009
08:18 AM
InstallScript Project!
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 02, 2009
09:17 AM
If you would had used a Basic MSI project, it would be easy to do.
You need to actually write a detection mechanism based on the products upgrade code.
When you find an older product of yours, you can set a property or global var.
Afterwards you can quit the installer when the property(or global var) is set.
You need to actually write a detection mechanism based on the products upgrade code.
When you find an older product of yours, you can set a property or global var.
Afterwards you can quit the installer when the property(or global var) is set.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 06, 2009
02:35 PM
Kotiomkin wrote:
Hi guys!
In the past I've written some setup projects customized for each customer. Every project include their specific files, attribute and so on.
Now, we find a way for use a single setup project for every our customer. But there is a problem: every old project has its own new GUID, so if I create this new setup project I suppose that when I will try to install it on a customer PC (that has an old project already installed) it could create problems!
So, since I know all the old GUIDs, can I create a sort of my "black list" in the new project in order to abort the new setup if I detect this old GUIDs?
If yes, what is the IS code for do this?
Other solutions are appreciated...
Thank you!
If you could afford to "Uninstall" old customer application then do followings
Create a array of your old GUID within your script
create a function that scans thorough all the GUIDs in an array and see if it exists on target system
if found then use the GUID to uninstall the existing applicaiton using LaunchAppAndWait
Once uninstalled, then continue installing that customer specific files.
HTH
![](/skins/images/3B39CE851FDD5528C393F146EB70A2D0/responsive_peak/images/icon_anonymous_message.png)