I'm re-authoring them from scratch.  Currently the merge modules are just a
small collection of file components, one of them being the service exe that
needs to be registered.  The service component looks like so:

<Component Id="DispatcherService.exe" Guid="hey-look-a-guid"
        SharedDllRefCount="no" KeyPath="no" NeverOverwrite="no" Permanent="no"
Transitive="no"
        Win64="no" Location="local">
<File Id="DispatcherService.exe" Name="DispatcherService.exe" 
        Source="$(var.DispatcherServiceFolder)\DispatcherService.exe" 
ReadOnly="no"
Compressed="yes"
        KeyPath="yes" Vital="yes" Hidden="no" System="no" Checksum="no" />
<ServiceInstall Id="DispatcherServiceInstall" Name="DispatcherService.exe"
        DisplayName="Dispatcher v.$(var.ProductVersion)"
        Description="Dispatcher Service for version $(var.ProductVersion)"
        ErrorControl="normal" Start="auto" Type="ownProcess"
        Vital="yes" Account="[ServiceLogonAccount]"
Password="[ServiceLogonPassword]" />
<ServiceControl Id="DispatcherServiceControl" Name="DispatcherService.exe"
        Start="install" Stop="uninstall" Remove="uninstall" />
</Component>




Blair-2 wrote:
> 
> How that is done really depends on the merge module. Who wrote those?
> 

-- 
View this message in context: 
http://n2.nabble.com/Setting-account-info-in-merge-module-from-MSI-dialog-tp3568432p3568743.html
Sent from the wix-users mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to