<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: binaries</title>
    <description>The latest articles on DEV Community by binaries (@binaries).</description>
    <link>https://dev.to/binaries</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F1040389%2F0c9308ee-0f40-46b1-adb7-146d4fe114e1.png</url>
      <title>DEV Community: binaries</title>
      <link>https://dev.to/binaries</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/binaries"/>
    <language>en</language>
    <item>
      <title>Force installation of unpublished Chrome extensions</title>
      <dc:creator>binaries</dc:creator>
      <pubDate>Tue, 28 Nov 2023 12:53:01 +0000</pubDate>
      <link>https://dev.to/binaries/force-installation-of-unpublished-chrome-extensions-1740</link>
      <guid>https://dev.to/binaries/force-installation-of-unpublished-chrome-extensions-1740</guid>
      <description>&lt;p&gt;How to install permanently your own unpublished Chrome extension from the Google Web Store on Chrome or Chromium-based browsers.&lt;/p&gt;

&lt;p&gt;The registry's ExtensionInstallAllowlist and ExtensionInstallForcelist make that possible.&lt;/p&gt;

&lt;p&gt;Here is inno-setup project.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://github.com/luxbin/force-install-chrome-extension"&gt;https://github.com/luxbin/force-install-chrome-extension&lt;/a&gt;&lt;/p&gt;

</description>
      <category>chromeextension</category>
      <category>forceinstall</category>
      <category>chrome</category>
      <category>permanently</category>
    </item>
    <item>
      <title>How to share data between different instance of same DLL</title>
      <dc:creator>binaries</dc:creator>
      <pubDate>Tue, 21 Nov 2023 14:30:41 +0000</pubDate>
      <link>https://dev.to/binaries/how-to-share-data-between-different-instance-of-same-dll-32pb</link>
      <guid>https://dev.to/binaries/how-to-share-data-between-different-instance-of-same-dll-32pb</guid>
      <description>&lt;p&gt;Usually Dlls are loaded into its corresponding process address space. Indeed the code is shared between all instances but not the global data. So the issue that we might face is – how can we share common data between all dll instances?&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;#pragma data_seg (".MYSEG")
    int g_nInteger = 0;
    char g_szString[] = "hello world";
#pragma data_seg()

// Tell the linker that the section
// .MYSEG is readable, writable and is shared.
#pragma comment(linker, "/SECTION:.MYSEG,RWS")
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Here we are declaring our data segment and are telling that, this segment is RWS – readable, writable and shared. This way we manage to share this data segment between all dll instances.&lt;/p&gt;

</description>
      <category>cpp</category>
    </item>
  </channel>
</rss>
