Why should we develop Code-first C# Plugins? Everything can be done in low-code, like Power Automate, Business Rules, classic Dynamics Workflows, etcetera, right? I will show you why we use plugins and give you hands-on experience with development. There are a lot of Questions for me to answer: 🔶 What are Plugins really, in this context? 🔶 Which type of Plugins? 🔶 When are they usually used? 🔶 Why are there layers of Plugins? 🔶 More details: What are the Steps? 🔶 Which flavors of Steps? 🔶 Should we care about Libraries & Base Classes? After this session - all Q:s ❓ are transcended to A:s ❗

Building tools for XrmToolBox is fun, easy, and rewarding. We will be ultra-hands-on to go through how to set up a new project, wire up the basic framework for our tool, and start building the logic by using features of the XrmToolBox development framework, and using my own share project to give custom controls for the Dataverse platform, and our collective ingenuity. Bring your ideas for a tool to this session, and we will start building it, from scratch!

What is ALM? I know it goes round and round and round... but there are a gazillion blogs, articles, and white papers and even from Microsoft themselves... both in general and specific in our area of the Power Platform. And everyone has various aspects. As for me myself - I'm lazy, as you probably know, I never want to do the same things twice. If it's possible to automate it - I'll do it! So I like to have good - or hopefully great - pipelines. Why is that? Having a great pipeline, we should never ever export/import solutions manually. We will never again forget to build it in Release mode. We will never try to import a solution without having the prereqs in the environment. We will never go to the production environment without having tested this next version. How do we do it? Again, there are a gazillion variations. How do you choose which way to do it? I'm not the God or mentor; I'm just a guy. A lazy guy. But come to this session to see how I do it!

Are you still writing your plugins from scratch, simply implementing the IPlugin interface? Are you using someone else’s framework, which isn’t really designed for your way of coding? Have you tried all the open source alternatives and still not found any favorite? Why not Build your own Plugin Base class?! It’s not hard, it doesn’t take weeks, and it helps you just the way you want it to help 😊 In this session I will show you 100% hands on how we can go from zero to plugin base hero for you and your team. We will start with a project with a few plugins, identify common/duplicated code, unnecessarily verbose code, and code where we simply feel that “this could be done so much easier with a little help”. From this we will create a Plugin Base class and some useful extension methods to SDK classes to finally clean up our plugins and enjoy the beauty of our refactored code.