You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you use XrmLibrary 's current assembly (between version 1.0 - 1.2) in a "Strong-named (signed)" project, the following error occurs in Visual Studio or in your application.
Could not load file or assembly 'XrmLibrary.EntityHelpers.2016, Version=1.2.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. A strongly-named assembly is required. (Exception from HRESULT: 0x80131044)
In fact, there is no bug or exception in XrmLibrary, Microsoft does not allow the using "un-signed" assemblies in a "Strong-named (signed)" assembly.
There are many alternative methods on the client side to solve this problem, but these are time consuming and require knowledge / experience.
That's why I created the "Strong-named (signed)" assembly version of XrmLibrary
If you already have a XrmLibrary nuget package (between version 1.0 - 1.2) in your project, you need to remove it and download "XrmLibrary.EntityHelpers.2016.Signed".
The text was updated successfully, but these errors were encountered:
When you use XrmLibrary 's current assembly (between version 1.0 - 1.2) in a "Strong-named (signed)" project, the following error occurs in Visual Studio or in your application.
In fact, there is no bug or exception in XrmLibrary, Microsoft does not allow the using "un-signed" assemblies in a "Strong-named (signed)" assembly.
There are many alternative methods on the client side to solve this problem, but these are time consuming and require knowledge / experience.
That's why I created the "Strong-named (signed)" assembly version of XrmLibrary
If you already have a XrmLibrary nuget package (between version 1.0 - 1.2) in your project, you need to remove it and download "XrmLibrary.EntityHelpers.2016.Signed".
The text was updated successfully, but these errors were encountered: