title: Can't debug PowerShell through Visual Studio
body: <p>I'm developing a binary PowerShell module. I've setup the debug tab of the module's project to launch the PowerShell console and import my module. If I press F5 it does so as expected. </p>
  
  <p><strong>The issue that I'm having is that Visual Studio isn't really "attached" to the process. The Modules window is empty and none of my break points are hit.</strong> </p>
  
  <p>If I launch PowerShell manually and attach to the process...<em>BOOM!</em> I can debug. </p>
  
  <p>F5ing would be wayyyy better than Build+Launch+Attach over and over again :|</p>
  
  <p>Any ideas?</p>
  
  <p>EDIT:</p>
  
  <p>I've found that if I enable unmanaged code debugging I will see modules loaded. This makes sense because PowerShell.exe is unmanaged. The issue now is that in the Modules window all of my assemblies Symbol States are "No native symbols in symbol file". The process "powershell.exe" is "Native" rather than "Managed (v2.0.50727)". It looks like VS is deciding to debug natively rather than in a managed mode. Any way to change this?</p>