Checkout http://blog.deploymentengineering.com/2006/07/msi-vs-net.html
   
  Basically a .NET service is no different from any other service from the 
service control managers and MSI's view.     ServiceBase is used to implement 
the contract but the ServiceInstaller class is completely unneeded.   
   
  The only catch you might see is a race condition with the way MSI publishes 
assemblies to the GAC/SxS storages.  If your service assembly has a dependency 
on these assemblies it can create a problem that seems to be a service problem 
but it isn't really.
  

Thomas Tomiczek <[EMAIL PROTECTED]> wrote:
                The old issue with “installutil” coming back, and this time for 
me it is not academic – I actually need to get two services rolled out and 
installed for a software package.
   
  I have to make two installers for .NET applications – one installs a system 
service straight, the other installs a system service and a website. The first 
installer may / should possibly not even have a UI (as it is supposed to be 
remote-installed by the server in admin mode, though we possibly leave the UI 
in for manual installation).
   
  Both installers are supposed to only work on Longhorn / Vista and with .NET 
3.5 installed (which I will check). Breaking the uninstall is not really a 
concern for this type of software (though it theoretically could be one, we are 
willing to take that risk and tell people to please reinstall the .net 
framework should something break.
   
  The services need to be set to autostart and run under local system account 
for now, though we think of some more elaborate setup later – point is that the 
silently installed service NEEDS local admin rights, and the other one needs 
domain admin rights, as they both are server remote control software (the local 
install an agent of the server doing certain thigns locally, while the server 
does certain things through the agent, but some directly, like maintenance of 
domain accounts).
   
  Naturally we use VS.NET 2008 for development ;) And Wix 3.0 is planned for 
the setup.
   
  What is the best way in this scenario to get the services installed? 
InstallUtil is still on the “don’t use” list? Any good code samples?
   
  I remember hefty discussions about this a long time ago (6-12 months) – now 
we have .NET 3.5, so, has something changed?
   
  Thanks in advance
   
  Thomas Tomiczek

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


       
---------------------------------
Be a better friend, newshound, and know-it-all with Yahoo! Mobile.  Try it now.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to