<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: DLL Compatibility on PharLap/LabVIEW RT in LabVIEW</title>
    <link>https://ni.lithium.com/t5/LabVIEW/DLL-Compatibility-on-PharLap-LabVIEW-RT/m-p/3747912#M1055152</link>
    <description>&lt;P&gt;mscoree.dll is the .Net core library. It means that your DLL is most likely a .Net assembly rather than a normal DLL and both .Net and ActiveX are definitely not something that will ever run on Pharlap.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Basically Pharlap supports the Win32 API from around Windows NT 4.0 without Unicode and user access control, file access security and other such features that are more targeted at server applications than embedded control. Anything introduced in later Windows versions except a few Windows 2000 APIs is basically not supported. That includes the complete .Net shenanigan. ActiveX is not supported since Microsoft&amp;nbsp;used this technology to protect its Windows operating system from people trying to clone it.&lt;/P&gt;</description>
    <pubDate>Tue, 30 Jan 2018 09:43:37 GMT</pubDate>
    <dc:creator>rolfk</dc:creator>
    <dc:date>2018-01-30T09:43:37Z</dc:date>
    <item>
      <title>DLL Compatibility on PharLap/LabVIEW RT</title>
      <link>https://ni.lithium.com/t5/LabVIEW/DLL-Compatibility-on-PharLap-LabVIEW-RT/m-p/3747605#M1055059</link>
      <description>&lt;P&gt;I have a DLL that I'd like to include in a RT application running on PharLap. &amp;nbsp;I've checked it with the NI DLL Checker and it flags the DLL bad as it internally makes calls to mscoree.dll&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;What DLLs are included in the PharLap subset of Win32? &amp;nbsp;Is anything which called mscoree.dll incompatible or do I need to point the DLL Checker tools to a different mscoree.dll than the one on my local Windows OS?&lt;/P&gt;</description>
      <pubDate>Mon, 29 Jan 2018 17:40:41 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/LabVIEW/DLL-Compatibility-on-PharLap-LabVIEW-RT/m-p/3747605#M1055059</guid>
      <dc:creator>blackburnite</dc:creator>
      <dc:date>2018-01-29T17:40:41Z</dc:date>
    </item>
    <item>
      <title>Re: DLL Compatibility on PharLap/LabVIEW RT</title>
      <link>https://ni.lithium.com/t5/LabVIEW/DLL-Compatibility-on-PharLap-LabVIEW-RT/m-p/3747861#M1055131</link>
      <description>&lt;P&gt;PharLap has pretty much all of ANSI C plus some NI specific functionalities. If you compile your DLL (from source) using LabVIEW CVI it tells you exactly what it is struggling with and you can replace those code sections with supported functionality (if possible). Also LabVIEW CVI has a list of all available libraries and functions and therefore is the easiest place to start.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 30 Jan 2018 07:40:15 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/LabVIEW/DLL-Compatibility-on-PharLap-LabVIEW-RT/m-p/3747861#M1055131</guid>
      <dc:creator>GoldenHunter</dc:creator>
      <dc:date>2018-01-30T07:40:15Z</dc:date>
    </item>
    <item>
      <title>Re: DLL Compatibility on PharLap/LabVIEW RT</title>
      <link>https://ni.lithium.com/t5/LabVIEW/DLL-Compatibility-on-PharLap-LabVIEW-RT/m-p/3747912#M1055152</link>
      <description>&lt;P&gt;mscoree.dll is the .Net core library. It means that your DLL is most likely a .Net assembly rather than a normal DLL and both .Net and ActiveX are definitely not something that will ever run on Pharlap.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Basically Pharlap supports the Win32 API from around Windows NT 4.0 without Unicode and user access control, file access security and other such features that are more targeted at server applications than embedded control. Anything introduced in later Windows versions except a few Windows 2000 APIs is basically not supported. That includes the complete .Net shenanigan. ActiveX is not supported since Microsoft&amp;nbsp;used this technology to protect its Windows operating system from people trying to clone it.&lt;/P&gt;</description>
      <pubDate>Tue, 30 Jan 2018 09:43:37 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/LabVIEW/DLL-Compatibility-on-PharLap-LabVIEW-RT/m-p/3747912#M1055152</guid>
      <dc:creator>rolfk</dc:creator>
      <dc:date>2018-01-30T09:43:37Z</dc:date>
    </item>
  </channel>
</rss>

