<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>.NET on Insinuator.net - Bold Statements</title>
    <link>https://insinuator.net/tags/.net/</link>
    <description>Recent content in .NET on Insinuator.net - Bold Statements</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 30 Apr 2018 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://insinuator.net/tags/.net/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Reversing and Patching .NET Binaries with Embedded References</title>
      <link>https://insinuator.net/2018/04/reversing-and-patching-.net-binaries-with-embedded-references/</link>
      <pubDate>Mon, 30 Apr 2018 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2018/04/reversing-and-patching-.net-binaries-with-embedded-references/</guid>
      <description>&lt;p&gt;Lately I’ve been analyzing a .NET binary that was quite interesting. It was a portable binary that shipped without any third-party dependencies. I started looking at the .NET assembly with ILSpy and noticed that there was not that much code that ILSpy found and there were a lot of references to classes/methods that were neither in the classes identified by ILSpy nor were they part of the .NET framework.&lt;/p&gt;&#xA;&lt;p&gt;At some point I was going through everything that ILSpy displayed about the binary, including the resources which were looking very interesting:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
