I don't think more disk space should be consumed if things are cabbed and the service executable is identical in the two Components (one Conditioned, the other not) because only one will ever get installed on the machine (due to mutually exclusive Conditions) and smart-cabbing should make sure only one file is in the cabinet.
(wow, that's one sentence <smile/>). On Mon, Feb 14, 2011 at 8:50 AM, Christopher Painter < chr...@deploymentengineering.com> wrote: > Technically it's a violation of the component rules. However, if you can > make > sure that the two components ( whether they be in two merge modules or no > merge > modules ) have mutually exclusive component conditions so that only one > will > ever be installed you can pretty much get away with it. You will still > get > validation errors as part of the build though I believe. I've done this in > the > past and my main complaint about it is it doesn't scale well. > > > If dev doesn't want to redo the app, what would be the effect of taking > consoleappservice.exe and copying / renaming it to have two files: > > consoleapp.exe > service.exe > > It's a confusing hack and you'll eat up more disk space then if you > factored it > out into the shared.dll but you should be able to still do everything I > mentioned previously. If this is .NET code it might not be happy but you > could > give it a try. > > Personally if it is a .NET service, I can't imagine it taking more then a > few > hours to factor out, build and test. > > --- > Christopher Painter, Author of Deployment Engineering Blog > Have a hot tip, know a secret or read a really good thread that deserves > attention? E-Mail Me > > > > ----- Original Message ---- > From: Gregg Swanson <gregg.swan...@microsoft.com> > To: General discussion for Windows Installer XML toolset. > <wix-users@lists.sourceforge.net> > Sent: Mon, February 14, 2011 10:38:26 AM > Subject: Re: [WiX-users] Conditionally invoking ServiceInstall Element > > Thanks for the help... > > I am a WIX rooky. > > Is this is a valid option - > > Package the consleappservice.exe in two separate merge modules, the first > doesn't invoke ServiceInstall the second does invoke ServiceInstall? > > The application that I am helping will have to refactor code and they may > be > reluctant to do so at this point in time. > > Thanks, > Gregg > > > -----Original Message----- > From: Christopher Painter [mailto:chr...@deploymentengineering.com] > Sent: Monday, February 14, 2011 10:14 AM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Conditionally invoking ServiceInstall Element > > The ServiceControl element is a child of the Component which is a child of > the > Feature element so the condition can be applied at the Feature or Component > level. If the component is installed the service will be installed and > there's > no way around that except to factor your service out of the console app: > > consleappservice.exe -> consoleapp.exe, service.exe, shared.dll > > Then you can put have Feature A reference the consoleapp.exe > and shared.dll > components and Feature B referene service.exe and shared.dll components. ( > Note: There is only 1 shared.dll component ) > > If feature B is installed you will get a service. If feature B is not > installed > you will not get a service but you can still have your console app if > feature A > is installed. > > >From a SysAdmin's point of view it's silent installs can be: > > msiexec /i foo.msi ADDLOCAL=A /qn or > msiexec /i foo.msi ADDLOCAL=A,B /qn > > If the service was not previously installed and now desired they can issue > the > command: > > msiexec /i foo.msi ADDLOCAL=B /qn > > If the service was previously installed and no longer desired they can > issue the > command > > msiexec /i foo.msi REMOVE=B /qn > > If they want to uninstall all together they can say: > > msiexec /x foo.msi /qn or > msiexec /i foo.msi REMOVE=ALL /qn > > > --- > Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, > know > a secret or read a really good thread that deserves attention? E-Mail Me > > > > ----- Original Message ---- > From: Gregg Swanson <gregg.swan...@microsoft.com> > To: "wix-users@lists.sourceforge.net" <wix-users@lists.sourceforge.net> > Sent: Mon, February 14, 2011 9:48:47 AM > Subject: [WiX-users] Conditionally invoking ServiceInstall Element > > Hello, > > I have a Console application that may also be used as a Windows Service. Is > it > possible to conditionally invoke or not invoke the ServiceInstall element > to > control when the service is installed? > > > Thanks, > Gregg > > ------------------------------------------------------------------------------ > The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: > Pinpoint memory and threading errors before they happen. > Find and fix more than 250 security defects in the development cycle. > Locate bottlenecks in serial and parallel code that limit performance. > http://p.sf.net/sfu/intel-dev2devfeb > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > > > > ------------------------------------------------------------------------------ > The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: > Pinpoint memory and threading errors before they happen. > Find and fix more than 250 security defects in the development cycle. > Locate bottlenecks in serial and parallel code that limit performance. > http://p.sf.net/sfu/intel-dev2devfeb > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > ------------------------------------------------------------------------------ > The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: > Pinpoint memory and threading errors before they happen. > Find and fix more than 250 security defects in the development cycle. > Locate bottlenecks in serial and parallel code that limit performance. > http://p.sf.net/sfu/intel-dev2devfeb > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > > > > ------------------------------------------------------------------------------ > The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: > Pinpoint memory and threading errors before they happen. > Find and fix more than 250 security defects in the development cycle. > Locate bottlenecks in serial and parallel code that limit performance. > http://p.sf.net/sfu/intel-dev2devfeb > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > -- virtually, Rob Mensching - http://RobMensching.com LLC ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
