Dynamics 365 CE online plugin error

[TkachouAndrej]

Category

• Bug

Describe the bug

Trying to use PnP framework (PnP.Core, PnP.Core.Auth) in D365 CE online plugin, faced with issue:

1. Sign my custom assembly and rebuild the project.
2. See warnings:
   Referenced assembly 'PnP.Core, Version=1.3.0.0, Culture=neutral, PublicKeyToken=null' does not have a strong name.
   Referenced assembly 'PnP.Core.Auth, Version=1.3.0.0, Culture=neutral, PublicKeyToken=null' does not have a strong name.
3. Try to run my custom assembly in debug mode via the plugin registration tool and see error:
   Could not load file or assembly 'PnP.Core, Version=1.3.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. > A strongly-named assembly is required. (Exception from HRESULT: 0x80131044)
4. Unsign my custom assembly and rebuild the project - no warnings. But we can't use unsigned assemblies as plugins.

Steps to reproduce

Sign PnP assemblies with strong key.

Expected behavior

Custom signed assembly could be used as CRM plugin.

Attachments

Visual studio 2017 warnings :

Plugin registration tool error :

Environment details (development & target environment)

• SDK version: [1.3.0]
• OS: [Windows 10]
• SDK used in: [.NET Assembly]
• Framework: [.NET Framework 4.6.1]
• Tooling: [Visual Studio 2017, Plugin Registration Tool]

[jansenbe]

Let me evaluate the options here @TkachouAndrej

[jansenbe]

@TkachouAndrej : I'm working on strong naming the assemblies, plan to finish today that work today so that you can test again with tomorrow's nightly build. Thanks for bringing this up.

[jansenbe]

@TkachouAndrej : version 1.3.52 and all future ones are strong named, so now you should be able to include the PnP Core SDK in your work.

[TkachouAndrej]

@jansenbe, when are you going to release 1.3.52? I can find only old 1.3.0 version in NuGet now. Thank you.

[jansenbe]

You need to allow preview versions to be used when querying nuget packages from visual studio or other IDEs

[TkachouAndrej]

@jansenbe, sorry, but I forgot to add PnP.Framework: the same issue

[jansenbe]

For PnP Framework the situation is more complex as it today uses a non strong names dependency... That would have to be remediated first. Do you have a hard dependency on PnP Framework?

[jansenbe]

Let's move this issue to the PnP Framework repo as that's what needs to be changed

[jansenbe]

@TkachouAndrej : the next nightly build of PnP Framework will be strong named