C#

As a Dynamics 365 (CRM) developer you have probably come to rely on the Dynamics CRM SDK over the years. With the release of Dynamics 365 Customer Engagement 9.0 (a.k.a. July 2017 Update) the old downloadable SDK has been replaced by an online document set and NuGet packages. This allows the SDK to become more of a living document where everyone is always referencing the most up-to-date information from Microsoft. Overall, I believe this is a big positive for developers which will make for a better development experience. ...

I’ve become a big fan of extension methods over the years to make my development work in Dynamics CRM, easier to implement and easier to read (i.e., easier to support.) Extension methods allow us to, exactly as the name implies, extended an existing class or interface with new methods - its a simpler version of implementing a derived class. Anyone familiar with developing .NET code for Dynamics CRM will be familiar with the IOrganizationService interface and its varied implementations. While in most cases I’m a fan of implementing my own version of IOrganizationService, often for code-base simplicity I’ll rely on some extension methods for my code. ...

Being able to use external DLLs in Dynamics CRM plugins is challenging but doable. Most people who have been doing development on the Dynamics CRM platform for any period of time know that it is not enough to simply reference the DLLs in Visual Studio - you must somehow make them available to run on the server - this can range from mildly annoying to impossible (if you using CRM Online.) ...

You are likely already familiar with the excellent development tool LINQPad and if you are a Dynamics CRM Developer you, hopefully, are familiar with LINQPad Plugin for Dynamics CRM. Using LINQPad along with the LINQPad CRM Plugin is a great way to learn the ins and outs of writing LINQ queries for Dynamics CRM. In this article I will show you how, with just a minimal of effort, you can start using LINQPad to directly call Dynamics CRM. This will allow you to go beyond just building LINQ queries and execute code to test Request/Response messages, QueryExpression retrieval, FetchXml, and much more. Using LINQPad allows you to test and learn in real-time without waiting to compile your code and execute your test cases (if you even have test cases! You do have test cases, right?) ...