<?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>SOS Best Practice: Match the SOS version with the process being analyzed</title><link>http://blogs.msdn.com/tom/archive/2008/08/25/sos-best-practice-match-the-sos-version-with-the-process-being-analyzed.aspx</link><description>I haven’t seen a whole of of issues around this as of yet, but now that 3.5 SP1 has released that may change.&amp;#160; If you copy SOS.dll to another location and then load it out of that directory to troubleshoot dumps, you may start seeing problems.&amp;#160;</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>a-foton &amp;raquo; SOS Best Practice: Match the SOS version with the process being analyzed</title><link>http://blogs.msdn.com/tom/archive/2008/08/25/sos-best-practice-match-the-sos-version-with-the-process-being-analyzed.aspx#8893667</link><pubDate>Mon, 25 Aug 2008 13:31:17 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8893667</guid><dc:creator>a-foton &amp;raquo; SOS Best Practice: Match the SOS version with the process being analyzed</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://blog.a-foton.ru/2008/08/sos-best-practice-match-the-sos-version-with-the-process-being-analyzed/"&gt;http://blog.a-foton.ru/2008/08/sos-best-practice-match-the-sos-version-with-the-process-being-analyzed/&lt;/a&gt;&lt;/p&gt;
</description></item></channel></rss>