<?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>Depends.exe and working with assembly dependencies</title><link>http://blogs.msdn.com/ianhu/archive/2006/07/17/668965.aspx</link><description>So in my last blog article I talked about using the fuslogvw.exe tool to figure out .NET assembly binding issues. In this article I’m going to look at another tool that I find myself using daily in the debugging world, depends.exe. In a nutshell, depends</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Interesting Finds: July 17, 2006</title><link>http://blogs.msdn.com/ianhu/archive/2006/07/17/668965.aspx#669099</link><pubDate>Tue, 18 Jul 2006 05:22:47 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:669099</guid><dc:creator>Jason Haley</dc:creator><description /></item></channel></rss>