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: Automation interface - component services
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
Feb 26, 2010
02:54 PM
Automation interface - component services
Finally getting around to trying to automate updating and building an existing InstallScript MSI project. This is also my first foray into using the automation interface, so please forgive the noobiness. I skimmed the automation interface stuff in help and nothing jumped out, so maybe I missed the obvious.
What I need to automate is the equivalent of going into the Component Services view in the IDE, right-clicking a currently-included complus component and choosing to 'refresh from system', then alter some of the settings back the way they were before the 'refresh', such as the 'runas' account info. This project is the server side of the complus picture. I also have a Basic MSI that has the proxy side of things that I'll want to automate.
Pointers into the doc appreciated, code examples would be absolutely wonderful.
Thanks,
Mike
What I need to automate is the equivalent of going into the Component Services view in the IDE, right-clicking a currently-included complus component and choosing to 'refresh from system', then alter some of the settings back the way they were before the 'refresh', such as the 'runas' account info. This project is the server side of the complus picture. I also have a Basic MSI that has the proxy side of things that I'll want to automate.
Pointers into the doc appreciated, code examples would be absolutely wonderful.
Thanks,
Mike
(1) Reply
Feb 27, 2010
08:10 PM
I don't believe that the automation interface exposes the ability. The UI isn't really that good either in that it expects the component service to be configured on the developer machine and then simply select it from the list.
Frankly I never really liked the way that IS handled this and if you search some of my old posts from 2005 you'll see that I found it better to just write my own custom actions to handle all of this.
I haven't had to do this since 2005 though as these days I use all .NET remoting technologies instead of COM.
Frankly I never really liked the way that IS handled this and if you search some of my old posts from 2005 you'll see that I found it better to just write my own custom actions to handle all of this.
I haven't had to do this since 2005 though as these days I use all .NET remoting technologies instead of COM.