Xrm.Sdk.PluginRegistration 3.1.1

There is a newer version of this package available.
See the version list below for details.
dotnet add package Xrm.Sdk.PluginRegistration --version 3.1.1                
NuGet\Install-Package Xrm.Sdk.PluginRegistration -Version 3.1.1                
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="Xrm.Sdk.PluginRegistration" Version="3.1.1" />                
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add Xrm.Sdk.PluginRegistration --version 3.1.1                
#r "nuget: Xrm.Sdk.PluginRegistration, 3.1.1"                
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
// Install Xrm.Sdk.PluginRegistration as a Cake Addin
#addin nuget:?package=Xrm.Sdk.PluginRegistration&version=3.1.1

// Install Xrm.Sdk.PluginRegistration as a Cake Tool
#tool nuget:?package=Xrm.Sdk.PluginRegistration&version=3.1.1                

Classic tool in XrmToolBox plugin form

Product Compatible and additional computed target framework versions.
.NET Framework net452 is compatible.  net46 was computed.  net461 was computed.  net462 was computed.  net463 was computed.  net47 was computed.  net471 was computed.  net472 was computed.  net48 was computed.  net481 was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
3.2024.3.2 21,359 3/2/2024
3.2023.12.14 14,338 12/21/2023
3.2023.12.12 2,664 12/15/2023
3.2023.12.7 1,363 12/14/2023
3.2023.12.3 3,046 12/11/2023
3.2023.12.2 2,010 12/8/2023
3.2023.11.1 9,109 11/6/2023
3.2023.10.2 7,904 10/11/2023
3.2023.9.3 5,504 9/28/2023
3.2022.12.2 40,409 12/12/2022
3.2022.12.1 1,489 12/11/2022
3.2022.4.1 36,167 4/3/2022
3.2021.6.1 38,715 6/9/2021
3.2021.4.1 9,998 4/4/2021
3.2021.3.2 2,786 3/29/2021
3.2020.12.1 12,997 12/8/2020
3.2020.11.3 5,224 11/19/2020
3.2020.11.2 2,691 11/16/2020
3.2020.9.1 8,999 9/28/2020
3.2020.5.2 15,402 5/8/2020
3.2020.5.1 2,542 5/6/2020
3.2020.4.15 3,905 4/23/2020
3.2020.4.14 1,376 4/23/2020
3.2020.1.4 11,572 1/29/2020
3.2019.7.1 18,495 7/14/2019
3.2018.11.4 12,616 11/8/2018
3.2018.8.3 23,169 8/27/2018
3.2018.7.22 7,786 7/13/2018
3.2017.8.1 62,370 8/3/2017
3.1.5.1 34,484 4/20/2017
3.1.4.2 52,269 1/31/2017
3.1.4.1 3,414 1/30/2017
3.1.4 5,481 1/26/2017
3.1.1 37,941 10/18/2016
3.0.9 16,387 8/15/2016
3.0.7 8,732 8/10/2016

Missing plugin checks added
   
There are kind of registration errors that really hard to debug. Usually they appear in error logs as Plug-in assembly does not contain the required types or assembly content cannot be updated.

Reasons causing the error could be different:

* Plugin get removed;
* Plugin get renamed;
* Plugin's access level modificator has changed.

But result is always the same: assembly could not be registered, since required plugin type is missing due to one of caused mentioned above.

Now this errors detected in PluginRegistration automatically. The code checks plugins listed in given assembly and in the CRM organization and in case of mismatch shows user list of plugins that causes the problem.