<?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 environment variables from CMD to PowerShell</title><link>http://blogs.msdn.com/jaybaz_ms/archive/2007/01/17/export-environment-variables-from-cmd-to-powershell.aspx</link><description>If you want to use PowerShell, but already have a CMD script that you want to keep, and that CMD script sets environment variables, you're in a pickle. Now I like pickles of all kinds, but Lee can help you get out of this one, with a script that exports</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: export environment variables from CMD to PowerShell</title><link>http://blogs.msdn.com/jaybaz_ms/archive/2007/01/17/export-environment-variables-from-cmd-to-powershell.aspx#1490153</link><pubDate>Thu, 18 Jan 2007 22:54:53 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1490153</guid><dc:creator>charlesalopez</dc:creator><description>&lt;p&gt;hey, how do i get an MSDN blog?&lt;/p&gt;
</description></item></channel></rss>