When I used the Fragment below, I noticed that the Windows service created
links to the *web.config* file as executable instead of linking to
MyServer.exe which is of course not a proper executable file and the
service fails to load understandably.
I moved the <File Source="Deliverables\web.config" /> line to a separate
Fragment and ComponentGroup and linked to that in the appropriate Feature
which solved the problem for me, yet I would like to understand better why
this occurred.
If I had wanted several files in this ComponentGroup yet created the
Windows service from the correct source file, how should the Fragment have
looked?
<Fragment> <ComponentGroup Id="MyServer" Directory="EFS">
<Component Id="MyServer.exe" Guid="my guid" Win64="yes">
<File Source="Deliverables\web.config" />
<File Id="MyServer.exe" Name="MyServer.exe" Source="Deliverables\
MyServer.exe" />
<ServiceInstall Id="ServiceInstaller" Type="
ownProcess" Name="MyServer"
DisplayName="MyServer"
Description="MyServer"
Start="auto" Account="[DOMAINUSER]"
Password="[PASSWORD]" ErrorControl="normal"
Arguments=" /start MyServer" />
<ServiceControl Id="StartService" Stop="both" Remove="uninstall"
Name="MyServer" Wait="yes" />
</Component> </ComponentGroup> </Fragment>
--
http://monochrome.me.uk/blog/
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
