<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Export and Import PowerShell ISE Opened Files</title><link>http://blogs.msdn.com/b/powershell/archive/2010/06/05/export-and-import-powershell-ise-opened-files.aspx</link><description>Unlike other tools, PowerShell ISE doesn&amp;rsquo;t have project files. Project files are a good way to set your environment up with a well known state. 
 Thanks to the ISE Object Model, it is possible to add some project functionality. 
 The script below</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: Export and Import PowerShell ISE Opened Files</title><link>http://blogs.msdn.com/b/powershell/archive/2010/06/05/export-and-import-powershell-ise-opened-files.aspx#10070468</link><pubDate>Fri, 01 Oct 2010 20:24:29 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:10070468</guid><dc:creator>Oisin G.</dc:creator><description>&lt;p&gt;If only it was possible to put the export into an event handler for powershell.exiting and the import into your profile. Unfortunately the asynchronous nature of eventing&amp;#39;s powershell.exiting means that the ISE OM is often disposed and/or GC&amp;#39;d before the event handler can read the files collection. Sigh.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10070468" width="1" height="1"&gt;</description></item></channel></rss>