3 Replies Latest reply on Nov 13, 2018 6:19 AM by Jonathan Muniz

Zebra.Printer.SDK InteropServices Exception

Walter Goydych Nov 2, 2018 1:10 PM

Hi Folks,

I’m a MS Visual Studio C# software developer & very new to Zebra SDK. Via Visual Studio package manager I downloaded NuGet package “Zebra.Printer.SDK 2.14.1989” into a simple Console Application project i.e. tried to use this SDK in Zebra’s simple example console program, as per Zebra doc. at “http://techdocs.zebra.com/link-os/2-14/pc_net/” (NB All the above target .NET 4.7.1)

The above fails with run time exception message of:-

“Could not load file or assembly 'System.Runtime.InteropServices.RuntimeInformation, Version=4.0.2.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified”

Any help would be appreciated. Thanks!

Re: Zebra.Printer.SDK InteropServices Exception

Jonathan Muniz Nov 9, 2018 6:39 AM (in response to Walter Goydych)

I had the same problem here.

The fix is pretty simple: edit the config file and on the node "dependentAssembly" where name attribute is "System.Runtime.InteropServices.RuntimeInformation", just remove the publicKeyToken attribute.

Hope that this fix it to you.
1 of 1 people found this helpful
Like Show 1 Likes(1)

Actions
Re: Zebra.Printer.SDK InteropServices Exception

Walter Goydych Nov 13, 2018 6:01 AM (in response to Walter Goydych)

Fixed this issue for me, thanks so much Jonathan!
Grateful if it’s easy for you, could you please point me to an explanation of what this issue really was & why your fix worked?
Like Show 0 Likes(0)

Actions
- Re: Zebra.Printer.SDK InteropServices Exception
  
  Jonathan Muniz Nov 13, 2018 6:19 AM (in response to Walter Goydych)
  
  Hello Walter!
  
  I think the error is not related with the Zebra SDK, but with the Microsoft InteropServices library, wich is a dependency to Zebra SDK works.
  I found the solution in a thread of StackOverflow, the same error was happening to MongoDB libraries, and the guys fixed.
  
  Visual Studio can't find the library when it has that hash code in the dependent assembly, if you remove it, just forces it to find in the referenced packages. This is just a workaround an I think Microsoft will fix this error soon.
  
  Regards,
  Jonathan
  
  Like Show 0 Likes(0)
  
  Actions

Go to original post