title: Using PowerShell with .NET 3.5 runtime/libraries
body: <p>Is it possible to run PowerShell 1.0 (or 2.0 CTP) backed by the 3.5 runtime instead of 2.0? </p>
  
  <p>We're building a .NET 3.5 solution, and I'd still like to use PowerShell as our scripting engine for scheduled tasks, etc. </p>
  
  <p>I don't need LINQ syntax or anything, just the 3.5 libraries and runtime.</p>
  
  <p>FOLLOWUP: thank you for the reply about dynamically loading assemblies. But let me clarify my question: is there any way to run PowerShell so that the 3.5 libraries run by default? So that if I enter <code>New-Object System.Xml.XmlDocument</code>, for example, I'm actually getting the 3.5 version by default? </p>
  
  <p>Semi-related question: if I <em>do</em> have to dynamically load, say, the <code>System.Xml</code> library from 3.5, will it <em>overlay</em> the existing symbol definitions such that the <em>next</em> time I type <code>New-Object System.Xml.XmlDocument</code>, it <em>will</em> load the 3.5 version?</p>