Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A strongly-named assembly is required #3

Closed
emregulcan opened this issue Aug 11, 2017 · 0 comments
Closed

A strongly-named assembly is required #3

emregulcan opened this issue Aug 11, 2017 · 0 comments

Comments

@emregulcan
Copy link
Owner

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".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant