Plug-ins 101: Simplifying plug-in development – part 1

It has been quite hectic the last weeks. We had a deadline to meet in the project we are working on. Today we were able to ship the solution.
A major part of the project was building plug-ins to offer the functionality the project desired. In this series of articles I want to share some of the things I came across.

As a CRM developer, you are limited in the technologies you can use. Literally every bit of code you develop that runs server side code is implemented as a plugin or action using the CRM SDK.

Writing plugins is a pretty straight forward task, however it is prone to errors.

  • execution stage (pre / post
  • synchronous/asynchronous
  • type of event (validate, create, update, delete, retrieve, retrievemultiple, setstate, execute)

Every time you write a plug-in, you have to deal with all these aspects. You have to do all plumbing by hand in order to get the plug-in to run.

A tedious task… 

Especially when working on large projects (but even on small projects) it can be handy to have a framework that handles the nuts and bolts. A framework that allows you to focus on the job instead of having to worry if the technical plugin implementation is correct.

In this new series of articles I will design and implement a basic framework that you can use in your projects. The code will be published under the MIT license on this blog.

As with every new journey, you have to prepare yourself for the things that might come on your path. In this journey, we have some reading to do:

Anyway time to do some reading… Stay tuned, more to come soon!

One thought on “Plug-ins 101: Simplifying plug-in development – part 1

Leave a Reply

Your email address will not be published. Required fields are marked *