Hello Sameer.
The error you are getting is because a "commit" custom action is to be run
inside the installation script.
And you give a contradictory command by telling

After='InstallFinalize'

Try changing that to

Before='InstallFinalize'

and you should get back in your feet with the linker.

However, do not overlook Pally's advice! try out the documented approach.

Regards!

2011/6/30 Pally Sandher <pally.sand...@iesve.com>

> Why not use the well documented method built into the ExitDialog as
> listed in the WiX 3.x manual? ->
> http://wix.sourceforge.net/manual-wix3/run_program_after_install.htm
>
> Palbinder Sandher
> Software Deployment Engineer
> T: +44 (0) 141 945 8500
> F: +44 (0) 141 945 8501
>
> http://www.iesve.com
> **Design, Simulate + Innovate with the <Virtual Environment>**
> Integrated Environmental Solutions Limited. Registered in Scotland No.
> SC151456
> Registered Office - Helix Building, West Of Scotland Science Park,
> Glasgow G20 0SP
> Email Disclaimer
> -----Original Message-----
> From: Rob Hamflett [mailto:r...@snsys.com]
> Sent: 30 June 2011 08:46
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] WiX noob: Starting an exe after installation.
>
> I don't think the 2826 error is the real problem.  It's more of a
> warning about your dialog layout.
>  I get that error in my logs too.  What does Windows Installer quote as
> the error in the error
> dialog, or is there something else reported later on in the log?
>
> The issue with your original custom action might be the fact that you've
> set Impersonate to 'yes'.
> I think after InstallFinalize, you're back to running as the user, so
> telling it to Impersonate
> might be tripping it up.  That's just a guess though, as it generally
> looks OK to me.
>
> Rob
>
> On 29/06/2011 19:30, Sameer Arora wrote:
> > What am I missing ?
> >
> > I would like the setup to launch my UI application after installation
> > completes successfully.
> >
> > My .wxs  files are modularized as:
> >
> > *InstallSequences.wxs*
> > <Fragment>
> > <InstallExecuteSequence>
> > ..
> >    <Custom Action="LaunchAppCA" After='InstallFinalize'>NOT
> > Installed</Custom>
> > ..
> > </InstallExecuteSequence>
> > </Fragment>
> >
> > *CustomActions.wxs*
> > <Fragment>
> > ..
> >              <CustomAction Id='LaunchAppCA' FileKey='[PathToMyExeApp]'
> > ExeCommand='' Return='asyncNoWait'  Impersonate='yes'
> Execute='commit'/>
> > ..
> > </Fragment>
> >
> >
> > Intention is to launch the application once the installation is
> successful
> > (hence Execute='commit') and not worry/wait for application's return
> value.
> >
> >
> > However, Light emits compile error:
> >
> >
> > *Installsequences.wxs*(29) : error LGHT0204: ICE77: LaunchAppCA is a
> > in-script custom action.  It must be sequenced in between the
> > InstallInitialize action and the InstallFinalize action in the
> > InstallExecuteSequence table.
> >
> > I also tried OnExit='success' but get the same error.
> > Of course it compiles fine when Before='InstallFinalize' but
> installation
> > fails with error below which I don't understand.
> > Info 2898.For VSI_MS_Sans_Serif13.0_0_0 textstyle, the system created
> a 'MS
> > Sans Serif' font, in 0 character set, of 13 pixels height.
> > DEBUG: Error 2826:  Control BannerBmp on dialog WelcomeForm extends
> beyond
> > the boundaries of the dialog to the right by 3 pixels
> > The installer has encountered an unexpected error installing this
> package.
> > This may indicate a problem with this package. The error code is 2826.
> The
> > arguments are: WelcomeForm, BannerBmp, to the right
> >
> >
> > I do have other custom actions defined in CustomAction.cs which are
> executed
> > in InstallExecuteSequence element but they are all Sequenced
> explicitly.
> >
> >
> > Appreciate any suggestion about what I could be missing or how I could
> > launch the app if installation succeeds.
> >
> > Thanks very much!
> > Sameer
> >
> ------------------------------------------------------------------------
> ------
> > All of the data generated in your IT infrastructure is seriously
> valuable.
> > Why? It contains a definitive record of application performance,
> security
> > threats, fraudulent activity, and more. Splunk takes this data and
> makes
> > sense of it. IT sense. And common sense.
> > http://p.sf.net/sfu/splunk-d2d-c2
>
>
> ------------------------------------------------------------------------
> ------
> All of the data generated in your IT infrastructure is seriously
> valuable.
> Why? It contains a definitive record of application performance,
> security
> threats, fraudulent activity, and more. Splunk takes this data and makes
>
> sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-d2d-c2
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
>
>
> ------------------------------------------------------------------------------
> All of the data generated in your IT infrastructure is seriously valuable.
> Why? It contains a definitive record of application performance, security
> threats, fraudulent activity, and more. Splunk takes this data and makes
> sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-d2d-c2
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>



-- 
Francisco Gabriel Malbrán
Licenciado en Ciencias de la Computación
Online CV: www.linkedin.com/in/franciscomalbran
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security 
threats, fraudulent activity, and more. Splunk takes this data and makes 
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to