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: Commit versus Commit In System Context
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
Jun 02, 2011
12:04 PM
Commit versus Commit In System Context
Okay for our new versions of our products we have gone to using Global assemblies for all our shared components and therefore a bunch of our custom actions require changes to the In-Script location/settings.
So my question is when to use Commit versus Commit in System Context?
All our installs require elevated Admin privileges to run and we also install services and device drivers with our installs. Oh and to compliate things more we are pushing out all these product installs as part of a Chained install package....
So my question is when to use Commit versus Commit in System Context?
All our installs require elevated Admin privileges to run and we also install services and device drivers with our installs. Oh and to compliate things more we are pushing out all these product installs as part of a Chained install package....
(3) Replies
![](/skins/images/A5EADE085F77DE82FB3B14D6B307AE6A/responsive_peak/images/icon_anonymous_message.png)
Not applicable
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jun 06, 2011
06:25 AM
System context sets the CA to run with elevated privilege. It is useful when we run the package on Vista\WIN 7 with UAC on.
But Remember you can’t roll back commit CAs.
But Remember you can’t roll back commit CAs.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jun 06, 2011
08:28 AM
Okay so in our case it does not matter if we use Commit Execution or Commit In System Context since our installs can only be ran as an Administrator.
Since we have multiple Global Assemblies that have to be registered on the system before we can trigger some of these custom actions we do not have much choice in In-Script Execution setting as Assemblies do not register on the system until after InstallFinalize and therefore we have to have these custom actions set as Commit, correct?
Since we have multiple Global Assemblies that have to be registered on the system before we can trigger some of these custom actions we do not have much choice in In-Script Execution setting as Assemblies do not register on the system until after InstallFinalize and therefore we have to have these custom actions set as Commit, correct?
![](/skins/images/A5EADE085F77DE82FB3B14D6B307AE6A/responsive_peak/images/icon_anonymous_message.png)
Not applicable
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jun 07, 2011
01:35 AM
“System Context” is required when you make system level changes on WIN7/Vista with UAC ON. It is applicable even if you make the setup execution level as admin.
Yes, you are correct, any assembly related CA should be scheduled after InstallFinalize and they can’t be rolled back.
Yes, you are correct, any assembly related CA should be scheduled after InstallFinalize and they can’t be rolled back.
![](/skins/images/A5EADE085F77DE82FB3B14D6B307AE6A/responsive_peak/images/icon_anonymous_message.png)