title: .Net Library and RFID Reader could I use to get NDEF message from NXP ICode SLIX?
body: <p>We would like to read NDEF records as well as Tag ID from our tags coming from production using any suitable .Net library. But as far as I saw this kind of NXP ICode SLIX seems to be poorly supported in the .Net community.</p>
  
  <p>Below are a couple of sample data screenshot from one of our tag, the first one helps to identify which kind of tag it is, the second one shows data we want to read underlined in red:</p>
  
  <p><a href="https://i.stack.imgur.com/CEALn.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/CEALn.png" alt="enter image description here"></a>
  <a href="https://i.stack.imgur.com/JrDxW.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/JrDxW.png" alt="enter image description here"></a></p>
  
  <p>We tried using several PC/SC lib like <a href="https://github.com/danm-de/pcsc-sharp" rel="nofollow noreferrer">pcsc-sharp</a> and <a href="http://cardwerk.com/smart-card-api/" rel="nofollow noreferrer">Smart Card API from Cardwerk</a> as well as <a href="https://github.com/Microsoft/Windows-universal-samples/tree/master/Samples/Nfc" rel="nofollow noreferrer">sample code from UWP</a> but our Identiv Multi-ISO reader seems to not operate APDU command to the card. </p>
  
  <p><strong>EDIT:</strong></p>
  
  <p>We have successfully tried an other RFID reader: an HID OmnyKey 5022 as suggested by a Cardwerk Engineer and NXP Support. It is working fine but only support Read Simple Block Command using <a href="https://github.com/danm-de/pcsc-sharp" rel="nofollow noreferrer">pcsc-sharp</a>.</p>
  
  <p>However If you could share some experience in reading NXP ICode Slix memory tag, and in particular NDEDF message using any .Net library with a proper RFID Reader it will be much appreciated.</p>
  
  <p>P.S.: This is an adapted version of a <a href="https://softwarerecs.stackexchange.com/q/49360/37726">question asked at Software Recommendations</a> and hesitate a bit before posting here because it may be too broad.</p>