<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>MacOS on DVLUP</title><link>/en/tags/macos/</link><description>Recent content in MacOS on DVLUP</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Thu, 31 Oct 2019 00:00:00 +0000</lastBuildDate><atom:link href="/en/tags/macos/index.xml" rel="self" type="application/rss+xml"/><item><title>Unblocking .NET DLLs on Mac Catalina</title><link>/en/blog/2019.10.31-unblocking-net-dlls-on-mac-catalina/</link><pubDate>Thu, 31 Oct 2019 00:00:00 +0000</pubDate><guid>/en/blog/2019.10.31-unblocking-net-dlls-on-mac-catalina/</guid><description>&lt;p&gt;There&amp;rsquo;s a new headache in town. If you run self-hosted Azure DevOps agent, or .NET Core project, on a Mac running Catalina (v 10.15+) and Microsoft Edge, you will have noticed a new behavior where the OS prevents the .NET assembly from working.&lt;/p&gt;&#10;&lt;p&gt;This is because it has been marked with a &amp;ldquo;quarantine&amp;rdquo; file attribute when it was downloaded with the browser. It&amp;rsquo;s a security measure that I&amp;rsquo;m familiar with on Windows. I would typically remove this attribute by right clicking on the file, select &amp;ldquo;Properties&amp;rdquo;, then check &amp;ldquo;Unblock&amp;rdquo;:&lt;/p&gt;</description></item></channel></rss>