How it works...

In the first three steps, we created a Visual Studio solution using the template included in the developer toolkit, and we gave it the name Packt.Xrm.Extensions, as per the first recipe in this chapter.

In step 4 to step 6, we opted to start from a Dynamics 365 solution. This will help us deploy our customization to an existing solution in Dynamics 365. Alternatively, we could have created a new solution.

In step 7 to step 9, we created a new project under the solution to hold our plugins. We could also create custom operations workflow activities or customization projects, each with a different set of libraries referenced. A sample code file is included in the plugin and custom workflow projects.

The Developer toolkit is currently in Beta release. It still has a few minor debugs that will hopefully be addressed in the final version. For instance, you will notice that the plugin project created is missing the dots in the namespace. This can easily be fixed by renaming the project and changing its properties.

In step 9, we ended up with a Visual Studio solution that contains two projects: a class library project for our plugins, and a CrmPackage project that contains our Dynamics 365 artefacts and an XML RegisterFile.crmregister that will help deploy our customization.

If you missed adding a project of a specific type during the initial setup, you can always add it later the normal way you add a project to your Visual Studio solution. The Dynamics 365 project templates will be available as demonstrated in step 3.

Table of Contents for How it works...

Create new playlist

Sign In

Sign Up

Table of Contents for
How it works...