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: Major Upgrade and GAC
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
‎Mar 02, 2010
06:41 PM
Major Upgrade and GAC
IS 2010
MSI Project
2 components
1 deployed to file system
1 deployed to GAC
Same source file
Install 1
Component registered in GAC
Component on file system
everything fine
Change Product Code
Have Major Upgrade item set
Build
Install
Component not registered in GAC
Component on file system
Repeat process
Component registered in GAC
Component on file system
What am I missing?
Thanks for any help
MSI Project
2 components
1 deployed to file system
1 deployed to GAC
Same source file
Install 1
Component registered in GAC
Component on file system
everything fine
Change Product Code
Have Major Upgrade item set
Build
Install
Component not registered in GAC
Component on file system
Repeat process
Component registered in GAC
Component on file system
What am I missing?
Thanks for any help
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 03, 2010
04:23 PM
Hi,
You may want to check out the following article:
Assemblies may be missing from the GAC or WinSxS cache after an MSI major upgrade
http://blogs.msdn.com/astebner/archive/2007/02/08/assemblies-may-be-missing-from-the-gac-or-winsxs-cache-after-an-msi-major-upgrade.aspx
It appears that you are running into some limitations of MSI behavior. One of the workarounds mentioned involves changing the sequencing for RemoveExistingProducts. Note that moving this action after InstallFinalize will likely require that you follow many of the minor upgrade rules such as not changing the component codes of existing components. Thus it is a more complicated placement.
-Ajay
You may want to check out the following article:
Assemblies may be missing from the GAC or WinSxS cache after an MSI major upgrade
http://blogs.msdn.com/astebner/archive/2007/02/08/assemblies-may-be-missing-from-the-gac-or-winsxs-cache-after-an-msi-major-upgrade.aspx
It appears that you are running into some limitations of MSI behavior. One of the workarounds mentioned involves changing the sequencing for RemoveExistingProducts. Note that moving this action after InstallFinalize will likely require that you follow many of the minor upgrade rules such as not changing the component codes of existing components. Thus it is a more complicated placement.
-Ajay
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 03, 2010
05:03 PM
Thank you very much. Sounds exactly like my problem.