title: How to create a Process that outlives its parent
body: <p>I'm trying to launch an external updater application for a platform that I've developed.  The reason I'd like to launch this updater is because my configuration utility which handles updates and license configuration for the platform has shared dependencies with other assemblies in the folder where the update will be deployed.  So, while I can rename the configuration utility and overwrite it when deploying the update, I can't rename or overwrite the DLLs it depends on.  Hence, the external updater application.</p>
  
  <p>I'm handling all of the update gathering logic in the configuration utility, then attempting to launch the updater to handle the actual file copy/overwrite operations.  Obviously, because of the file in use issues, I need the configuration utility to exit right after the updater begins.</p>
  
  <p>The problem I'm having is that I'm using the standard Process.Start method of launching the updater, and as soon as the configuration utility exits, the updater process gets killed too.</p>
  
  <p>Is there any way that I can create a Process that outlives its parent, or launch an external application that can run beyond the program that launched it?</p>
  
  <p>EDIT:</p>
  
  <p>Apparently, in my updater application, I miscalculated the number of command line arguments which are passed to it.  Because of this, the updater would exit immediately.  I misinterpreted this to mean that the launcher application was killing the "child" process, when in fact, it wasn't.</p>
  
  <p>The answers below are correct.</p>