XrmPluginCore provides base functionality for developing plugins and custom APIs in Dynamics 365. It includes context wrappers and registration utilities to streamline the development process.
- Context Wrappers: Simplify access to plugin execution context.
- Registration Utilities: Easily register plugins and custom APIs.
- Compatibility: Supports .NET Standard 2.0, .NET Framework 4.6.2, and .NET 8.
- Create a new class that inherits from
Plugin
. - Register the plugin using the
RegisterPlugin
helper methods. - Implement the function in the custom action
namespace Some.Namespace {
using System;
using XrmFramework.BusinessDomain.ServiceContext;
using XrmPluginCore;
using XrmPluginCore.Enums;
public class AccountChainPostPlugin : Plugin {
public AccountChainPostPlugin() {
RegisterStep<Account>(
EventOperation.Update,
ExecutionStage.PostOperation,
ExecutePlugin)
.AddFilteredAttributes(x => x.Fax);
}
protected void ExecutePlugin(IServiceProvider serviceProvider) {
var serviceFactory = serviceProvider.GetService<IOrganizationServiceFactory>();
var executionContext = serviceProvider.GetService<IPluginExecutionContext>();
var service = serviceFactory.CreateOrganizationService(executionContext.UserId);
var rand = new Random();
var newAcc = new Account(localContext.PluginExecutionContext.PrimaryEntityId) {
Fax = rand.Next().ToString()
};
service.Update(newAcc);
}
}
}
NOTE It is recommended to use dependency injection based plugins instead of blindly using the IServiceProvider. See the example in XrmBedrock, or the sample plugin in the test project for more information.
namespace Some.Namespace {
using System;
using XrmFramework.BusinessDomain.ServiceContext;
using XrmPluginCore;
using XrmPluginCore.Enums;
public class AccountChainPostPlugin : Plugin {
public AccountChainPostPlugin() {
RegisterPluginStep<Account>(
EventOperation.Update,
ExecutionStage.PostOperation,
ExecutePlugin)
.AddFilteredAttributes(x => x.Fax);
}
protected void ExecutePlugin(LocalPluginContext localContext) {
if (localContext == null) {
throw new ArgumentNullException("localContext");
}
var service = localContext.OrganizationService;
var rand = new Random();
var newAcc = new Account(localContext.PluginExecutionContext.PrimaryEntityId) {
Fax = rand.Next().ToString()
};
service.Update(newAcc);
}
}
}
Use XrmSync to automatically register relevant plugin steps and images.
XrmPluginCore and XrmSync does not currently support Dependent Assemblies. If your plugin depends on other assemblies, you can use ILRepack or a similar tool to merge the assemblies into a single DLL before deploying.
To ensure XrmPluginCore, and it's dependencies are included, you can use the following settings for ILRepack:
<Target Name="ILRepack" AfterTargets="Build">
<ItemGroup>
<InputAssemblies Include="$(TargetPath)" />
<InputAssemblies Include="$(TargetDir)Microsoft.Bcl.AsyncInterfaces.dll" />
<InputAssemblies Include="$(TargetDir)Microsoft.Extensions.DependencyInjection.Abstractions.dll" />
<InputAssemblies Include="$(TargetDir)Microsoft.Extensions.DependencyInjection.dll" />
<InputAssemblies Include="$(TargetDir)XrmPluginCore.Abstractions.dll" />
<InputAssemblies Include="$(TargetDir)XrmPluginCore.dll" />
</ItemGroup>
<Exec Command="$(PkgILRepack)\tools\ILRepack.exe /parallel /keyfile:[yourkey].snk /lib:$(TargetDir) /out:$(TargetDir)ILMerged.$(TargetFileName) @(InputAssemblies -> '%(Identity)', ' ')" />
</Target>
Contributions are welcome! Please submit a pull request or open an issue to discuss your ideas.
This project is licensed under the MIT License.