<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>debugging &amp;mdash; Attach to Process</title>
    <link>https://devblog.dinobansigan.com/tag:debugging</link>
    <description>Thoughts and Notes on Software Development</description>
    <pubDate>Thu, 16 Apr 2026 12:23:44 +0000</pubDate>
    <image>
      <url>https://i.snap.as/4wmUdb6N.png</url>
      <title>debugging &amp;mdash; Attach to Process</title>
      <link>https://devblog.dinobansigan.com/tag:debugging</link>
    </image>
    <item>
      <title>To prevent an unsafe abort when evaluating the function &#34;Moq.Internals.InterfaceProxy.ToString()&#34;</title>
      <link>https://devblog.dinobansigan.com/to-prevent-an-unsafe-abort-when-evaluating-the-function?pk_campaign=rss-feed</link>
      <description>&lt;![CDATA[Was getting this error from Visual Studio 2022 while debugging a unit test.&#xA;Moq error in Visual Studio 2022&#xA;&#xA;The solution for me was to uncheck the &#34;Call string-conversion function on objects in variables windows&#34; checkbox.&#xA;Solution for Moq error in Visual Studio 2022&#xA;&#xA;Tags: #Debugging #Moq #Tests #VisualStudio&#xA;&#xA;a href=&#34;https://remark.as/p/devblog.dinobansigan.com/to-prevent-an-unsafe-abort-when-evaluating-the-function&#34;Discuss.../a or leave a comment below.]]&gt;</description>
      <content:encoded><![CDATA[<p>Was getting this error from Visual Studio 2022 while debugging a unit test.
<img src="https://i.snap.as/1ywkq6ZW.png" alt="Moq error in Visual Studio 2022"/></p>

<p>The solution for me was to uncheck the “Call string-conversion function on objects in variables windows” checkbox.
<img src="https://i.snap.as/I7Eaxx8y.png" alt="Solution for Moq error in Visual Studio 2022"/></p>

<p>Tags: <a href="https://devblog.dinobansigan.com/tag:Debugging" class="hashtag"><span>#</span><span class="p-category">Debugging</span></a> <a href="https://devblog.dinobansigan.com/tag:Moq" class="hashtag"><span>#</span><span class="p-category">Moq</span></a> <a href="https://devblog.dinobansigan.com/tag:Tests" class="hashtag"><span>#</span><span class="p-category">Tests</span></a> <a href="https://devblog.dinobansigan.com/tag:VisualStudio" class="hashtag"><span>#</span><span class="p-category">VisualStudio</span></a></p>

<p><strong><a href="https://remark.as/p/devblog.dinobansigan.com/to-prevent-an-unsafe-abort-when-evaluating-the-function">Discuss...</a></strong> or leave a comment below.</p>
]]></content:encoded>
      <guid>https://devblog.dinobansigan.com/to-prevent-an-unsafe-abort-when-evaluating-the-function</guid>
      <pubDate>Tue, 09 Jul 2024 19:36:00 +0000</pubDate>
    </item>
    <item>
      <title>Breakpoint Failed to Bind - Visual Studio 2017</title>
      <link>https://devblog.dinobansigan.com/breakpoint-failed-to-bind-visual-studio-2017?pk_campaign=rss-feed</link>
      <description>&lt;![CDATA[Today I ran into an issue where I was trying to debug an application and I was getting a &#34;Breakpoint failed to bind&#34; error on Visual Studio 2017. I was trying to attach to the process when I got the error. I was already running in Administrator mode, so it wasn&#39;t a permissions issue.&#xA;&#xA;Solution&#xA;&#xA;Turns out I had the solution configuration set to &#34;Release&#34; right from the start. The fix then was to set the solution configuration to &#34;Debug&#34; and then rebuild the solution. After that, I was able to attach to the process with no errors whatsoever.&#xA;&#xA;Reference:&#xA;https://stackoverflow.com/questions/31732944/breakpoint-failed-to-bind-visual-studio-2015&#xA;&#xA;#VisualStudio #Debugging&#xA;&#xA;a href=&#34;https://remark.as/p/devblog.dinobansigan.com/breakpoint-failed-to-bind-visual-studio-2017&#34;Discuss.../a or leave a comment below.]]&gt;</description>
      <content:encoded><![CDATA[<p>Today I ran into an issue where I was trying to debug an application and I was getting a “Breakpoint failed to bind” error on Visual Studio 2017. I was trying to attach to the process when I got the error. I was already running in Administrator mode, so it wasn&#39;t a permissions issue.</p>

<h3 id="solution" id="solution">Solution</h3>

<p>Turns out I had the solution configuration set to “Release” right from the start. The fix then was to set the solution configuration to “Debug” and then rebuild the solution. After that, I was able to attach to the process with no errors whatsoever.</p>

<h3 id="reference" id="reference">Reference:</h3>

<p><a href="https://stackoverflow.com/questions/31732944/breakpoint-failed-to-bind-visual-studio-2015">https://stackoverflow.com/questions/31732944/breakpoint-failed-to-bind-visual-studio-2015</a></p>

<p><a href="https://devblog.dinobansigan.com/tag:VisualStudio" class="hashtag"><span>#</span><span class="p-category">VisualStudio</span></a> <a href="https://devblog.dinobansigan.com/tag:Debugging" class="hashtag"><span>#</span><span class="p-category">Debugging</span></a></p>

<p><strong><a href="https://remark.as/p/devblog.dinobansigan.com/breakpoint-failed-to-bind-visual-studio-2017">Discuss...</a></strong> or leave a comment below.</p>
]]></content:encoded>
      <guid>https://devblog.dinobansigan.com/breakpoint-failed-to-bind-visual-studio-2017</guid>
      <pubDate>Thu, 13 Dec 2018 00:00:00 +0000</pubDate>
    </item>
  </channel>
</rss>