<?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/" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"><channel><title>PowerShell StdOut go out, StdErr go everywhere</title><link>http://blogs.msdn.com/b/jenss/archive/2013/02/14/powershell-stdout-go-out-stderr-go-everywhere.aspx</link><description>While becoming familiar and a really big fan of PowerShell, I faced the following issue. During a migration project doing bulk migrations, I needed information Messages (coming to StdOut) as well as error message (coming to StdErr) displayed to the Console</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator></channel></rss>