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: Assembly question...
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
‎Jun 13, 2006
08:36 AM
Assembly question...
Not sure if anyone has encountered the need for this, but...
I have an assembly that is used by several product installs that lays down some common files and performs some tasks during install. I would like to support upgrading the product and have the upgraded product re-execute the assembly installation (i.e. like a Replace property of "always replace"), so that the common tasks can be run again.
From what I can tell, this doesn't seem to be possible unless the assembly's version is updated and I include the updated assembly.
Am I wrong here? Is there a way to have a product install force an assembly to install/replace without having the assembly have an incremented version?
Daniel
I have an assembly that is used by several product installs that lays down some common files and performs some tasks during install. I would like to support upgrading the product and have the upgraded product re-execute the assembly installation (i.e. like a Replace property of "always replace"), so that the common tasks can be run again.
From what I can tell, this doesn't seem to be possible unless the assembly's version is updated and I include the updated assembly.
Am I wrong here? Is there a way to have a product install force an assembly to install/replace without having the assembly have an incremented version?
Daniel
(2) Replies
‎Sep 04, 2006
08:48 AM
danquo wrote:
Not sure if anyone has encountered the need for this, but...
I have an assembly that is used by several product installs that lays down some common files and performs some tasks during install. I would like to support upgrading the product and have the upgraded product re-execute the assembly installation (i.e. like a Replace property of "always replace"), so that the common tasks can be run again.
From what I can tell, this doesn't seem to be possible unless the assembly's version is updated and I include the updated assembly.
Am I wrong here? Is there a way to have a product install force an assembly to install/replace without having the assembly have an incremented version?
Daniel
I think you are correct and I too am having this issue. I have an assembly with 2 sub-features. Once one of features is installed I am unable to install the other. Probably due to the main UUID for the assembly being detected in the vpd. 😞
‎Sep 07, 2006
02:15 PM
I Second you guys on the same problem.
I pretty much have the same issue.
I have two features, each one having a assembly. the installer product launches the first assembly and screens come up fine, but it never launches the second asseumbly...
but when it comes to the pre-install summary screen, it says it will install both the features and also runs both the assemblies.
my question here is, how should i tell the installer to launch both the assemblies when i have both the features selected.
as per the help that IS provides, this seems to be a pretty standard feature that installshield has and should work without any issues.
may be i am doing something wrong here or may be IS folks areb*llshi**ing... :mad: :mad:
I pretty much have the same issue.
I have two features, each one having a assembly. the installer product launches the first assembly and screens come up fine, but it never launches the second asseumbly...
but when it comes to the pre-install summary screen, it says it will install both the features and also runs both the assemblies.
my question here is, how should i tell the installer to launch both the assemblies when i have both the features selected.
as per the help that IS provides, this seems to be a pretty standard feature that installshield has and should work without any issues.
may be i am doing something wrong here or may be IS folks areb*llshi**ing... :mad: :mad: