Sample repo you can use to experiment with the different versions of FakeXrmEasy

This is the supporting code for a the following scenario :

In order to build and debug the solution you will need:

• .NET 4.6.2 and the associated Developer Pack installed
• .net 6.0 sdk installed https://dotnet.microsoft.com/en-us/download/dotnet/6.0
• dotnet setup instrucions on Ubuntu 22.04: dotnet/core#7699

This sample repo shows how to combine FakeXrmEasy versions 2 and 3 to dev and test both a plugin project that uses the CoreAssemblies sdk (.net 4.6.2), and an azure functions project that uses the DataverseClient nuget package (.net6.0).

By using a shared project (or a git submodule, or a nuget package with source files), we can dev, test, and even debug server side code (plugins) from client apps right from the same debugging session.

You'll find an overview of why / how this project is structured in the docs here How to migrate a v3 Azure function to v4 Azure function

• 1. We receive some contactdata into an Azure Function
• 2. The Azure function creates a Contact using DataverseClient nuget package in .net core
• 3. A plugin that fires on create of that contact record and creates a follow up Task.

In the demo we approached unit testing such scenario as follows:

• 1. A unit test to validate that the contact data is sent to Dataverse correcly (the contact is created)
• 2. A unit test to verify the plugin creates a follow up task given a Create message with an OutputParameter (the resulting from the Create operation) was received
• 3. A pipeline simulation scenario that wires everything together In-Memory, to check that both the contact and the task are created (this is experimental stuff, because really, the target versions of the client (.net core 3.1) and the server (net462) are different in production, but eventually....)

The Azure function project targets net3.1, but the plugins project targets net462 so bear in mind you'll need a Windows machine to build the whole solution

From the command line:

dotnet restore
dotnet build
dotnet test

Alternatively from VS and Test Explorer

You'll find the sample code for automatic registration with Spkl under the /spkl directory.

Also please make sure to check out the relevant documentation

The FakeXrmEasy.Samples.sln also has a running example of a custom api.

Please check the docs for high level overview of Messages, Custom Actions, and Custom Apis.

Check out the latest release notes of FakeXrmEasy you don't miss any impotant updates!

• https://dynamicsvalue.github.io/fake-xrm-easy-docs/releases/2x/
• https://dynamicsvalue.github.io/fake-xrm-easy-docs/releases/3x/

This repo is available under the FakeXrmEasy's LICENSE.

Basically, you can use FakeXrmEasy free of charge:

• In Open Source Projects and/or
• For a Non-Commercial use and/or
• As part of a Non-Commercial Organization

You'll need a commercial license for propietary and commercial use.

Please, have a look at our licensing FAQ for more details.

Pricing: https://dynamicsvalue.com/pricing