[wix-users] COM Object exception

[Hoover, Jacob]

WixStdBA already does this. Have a look @ OnExecuteMsiMessage. Note if you want super detailed progress you need a custom them that includes a ExecuteProgressActionDataText control.

-----Original Message-----
From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of Alex Tuppen
Sent: Wednesday, February 22, 2017 3:35 AM
To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
Subject: Re: [wix-users] COM Object exception

Feedback from the install progress and messages, what is the best way to pass that back?

On Tue, 21 Feb 2017 at 23:20 Hoover, Jacob <Jacob.Hoover at greenheck.com>
wrote:

> Define information?  If you are using burn, normally the BA would 
> collect any configuration information and pass it to the MSI as a 
> property. If you are talking about feedback from the install progress 
> and messages, then yes. If you are using DisplayInternalUI then no.
>
> -----Original Message-----
> From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On 
> Behalf Of Alex Tuppen
> Sent: Tuesday, February 21, 2017 3:38 PM
> To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
> Subject: Re: [wix-users] COM Object exception
>
> That makes sense, is it possible to pass information from an MSI back 
> to bootstrapper for the GUI?
>
> On Tue, 21 Feb 2017 at 19:53 Hoover, Jacob 
> <Jacob.Hoover at greenheck.com>
> wrote:
>
> > You could create a MSI with your configuration in it and put it in 
> > the chain after the MMA MSI.
> >
> > -----Original Message-----
> > From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On 
> > Behalf Of Alex Tuppen
> > Sent: Tuesday, February 21, 2017 1:36 PM
> > To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
> > Subject: Re: [wix-users] COM Object exception
> >
> > Are there any options if the MSI I am installing is not one that I 
> > have made? I looked at custom actions but I can't run those in the 
> > bundle itself. Basically I am just installing the MMA and then 
> > configuring it to point to Azure where the actual work is done 
> > (hence why I am not installing anything that i have written).
> >
> > On Tue, 21 Feb 2017 at 17:54 Phill Hogland 
> > <phill.hogland at rimage.com>
> > wrote:
> >
> > > A BA should not try to implement any configuration changes.  You 
> > > might look at using a DTF CA in a chained MSI or as there is a 
> > > similar PowerShell script posted in the following link then 
> > > consider using the
> > Wix PSExtension.
> > >
> > > ________________________________
> > > From: wix-users <wix-users-bounces at lists.wixtoolset.org> on behalf 
> > > of Alex Tuppen <alex.tuppen at gmail.com>
> > > Sent: Tuesday, February 21, 2017 10:37:54 AM
> > > To: wix-users at lists.wixtoolset.org
> > > Subject: [wix-users] COM Object exception
> > >
> > > Hi,
> > >
> > > I was wondering if there is anything that I need to do to be able 
> > > to use a COM object from within a custom bootstrapper. I have the 
> > > same COM object working outside the bootstrapper but no matter 
> > > what I try it always throws an exception when the bootstrapper tries to use it.
> > >
> > > The COM object in question is for the Microsoft Monitoring Agent 
> > > and is registered when the MMA is installed. I am attempting to 
> > > use it with the following code:
> > >
> > >         public async Task<string> ConfigureOMSAgent()
> > >         {
> > >             return await Task.Run(() =>
> > >             {
> > >                 try
> > >                 {
> > >                     // Load COM object
> > >                     Bootstrapper.Engine.Log(LogLevel.Verbose,
> > > "Loading ManagementServiceConfiguration COM object");
> > >
> > > AgentConfigManagerLib.ManagementServiceConfiguration
> > > mgmntSrvCnfg = new
> > AgentConfigManagerLib.ManagementServiceConfiguration();
> > >                     // Configuring MMA as OMS agent
> > >                     Bootstrapper.Engine.Log(LogLevel.Verbose,
> > > "Configuring MMA as OMS agent");
> > >                     mgmntSrvCnfg.AddCloudWorkspace(WorkSpaceID,
> > > WorkSpaceKey);
> > >                     // Return empty string indicating success
> > >                     return string.Empty;
> > >                 }
> > >                 catch (Exception e)
> > >                 {
> > >                     ErrorThrown(e.Message);
> > >                     return e.Message;
> > >                 }
> > >             });
> > >         }
> > >
> > > Any help will be amazing!
> > >
> > > Thank you,
> > >
> > > Alex
> > >
> > > __________________________________________________________________
> > > __ WiX Toolset Users Mailing List provided by FireGiant 
> > > http://www.firegiant.com/
> > >
> > > __________________________________________________________________
> > > __ WiX Toolset Users Mailing List provided by FireGiant 
> > > http://www.firegiant.com/
> > >
> >
> > ____________________________________________________________________
> > WiX Toolset Users Mailing List provided by FireGiant 
> > http://www.firegiant.com/
> >
> > ____________________________________________________________________
> > WiX Toolset Users Mailing List provided by FireGiant 
> > http://www.firegiant.com/
> >
>
> ____________________________________________________________________
> WiX Toolset Users Mailing List provided by FireGiant 
> http://www.firegiant.com/
>
> ____________________________________________________________________
> WiX Toolset Users Mailing List provided by FireGiant 
> http://www.firegiant.com/
>

____________________________________________________________________
WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/