<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="../assets/xml/rss.xsl" media="all"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Drylm - Thoughts from the void. (Posts about fuslogvw)</title><link>https://blog.drylm.org/</link><description></description><atom:link href="https://blog.drylm.org/categories/fuslogvw.xml" rel="self" type="application/rss+xml"></atom:link><language>en</language><lastBuildDate>Sun, 28 Dec 2025 14:59:07 GMT</lastBuildDate><generator>Nikola (getnikola.com)</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>Debug dotnet applications inside a docker container</title><link>https://blog.drylm.org/posts/debug-dotnet-applications-inside-a-docker-container/</link><dc:creator>Jonathan Muller</dc:creator><description>&lt;div&gt;&lt;p&gt;From time to time, as a dotnet developer we have to face this specific error &lt;strong&gt;Could not load file or assembly 'Assembly Strong Name' or one of its dependencies&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;To help debugging this particular situation, Microsoft provides a tool in the .net SDK called: &lt;em&gt;fuslogvw&lt;/em&gt;.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://blog.drylm.org/posts/debug-dotnet-applications-inside-a-docker-container/"&gt;Read more…&lt;/a&gt; (1 min remaining to read)&lt;/p&gt;&lt;/div&gt;</description><category>.net</category><category>c#</category><category>csharp</category><category>docker</category><category>fuslogvw</category><category>powershell</category><guid>https://blog.drylm.org/posts/debug-dotnet-applications-inside-a-docker-container/</guid><pubDate>Sat, 10 Feb 2018 09:26:25 GMT</pubDate></item></channel></rss>