<?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>Episode 50 of Visual Studio Toolbox: Collecting IntelliTrace Data in Production</title><link>http://blogs.msdn.com/b/robertgreen/archive/2012/10/03/episode-49-of-visual-studio-toolbox-collecting-intellitrace-data-in-production.aspx</link><description>IntelliTrace is a great tool. It records and traces your app's code execution and stores this information in a trace file. You can open up that trace file later on and figure out why your app isn't behaving as expected. This can save you huge amounts</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator></channel></rss>