RappSack - my rucksack contains all I need, and nothing else.

For us, developers in C#, there are a gazillion plus three libraries, frameworks, helpers, and utilities available.

But what do they do? Do you understand the core of our lovely area, the Power Platform? Are you on top of the SDK? You should be...

I'm the first to admit that I don't know everything about the Microsoft.CrmSdk.CoreAssemblies. But now that I know I know enough, I realize I have to get some sort of library.

Developing only on the core SDK makes me want to shift my career and start up an ice cream boutique instead.

Some companies have remarkable, huge frameworks, with so many layers on layers that completely hide the fact that we are actually working with Dataverse. It's fantastic for those who don't really like the Power Platform (who's that??) to say that they are only working in C#, period.

I like Power Platform.
I want to KNOW Power Platform, Dataverse, and the SDK.

A rucksack is perfect. It is not in the way of my hands, so I can still be coding, easy to carry, and a big sack with important, core, fundamental things in it. The rucksack also has some small pockets with some small gadgets, with different types in each pocket.

You see where I'm going...?

The RappSack is my non-physical rucksack.
The big sack implements IOrganizationService and logging.
A medium sack inherits the big one, and implements IPlugin and ITracingService.
One pocket can make everything early bound.
Another pocket lets you get and write Environment Variables with smart types.
It's easy to carry it as a shared project in an open-source git repository.
It's easy to select which things in the sack I will use.
It's easy to improve the RappSack.

In this session, I will show—live—how we start implementing your own type of libraries, explain why it should be a shared project, and then dig into the RappSack at the end.

Dataverse Plugin Solves Everything

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 ❗

🛞 ALM a la Rapp - What we should, shouldn't, must!

What's the buzz with ALM?
Everyone is talking about it now.
But do you really know what it means, and do you know the important parts?

I probably don't know either, but during this session, I will show you what I think is important.

As my profile says, I want to help you all to be as lazy as I am, to make you able to focus on the fun part at work, not the boring crappy parts - just automate it for us and confirm the quality! Automagically!

A good start is to have a proper pipeline to build everything. Step two is to have a pipeline to deploy it to any target environment.

How to create a good, proper pipeline?
Well, join me.

How do we do it? There are a gazillion variations. How do you choose which way to do it? I'm not God; I don't have The Answer; I'm just a random, guy sitting in the corner, and having opinions.

My journey back to life after the stroke

I am Jonas.
I was a coder, a colleague, knowing the all, a presenter, a happy player, and a MVP.
I was a runner and an active, sporty guy and an excellent skier.
One year ago, I got a stroke.
It removed everything from me. Everything.
Since 16 February, the journey back to a normal life is long. Lots of work work work, to get back everything I remember.
The stroke hit me physically.
And it hit my communication.
I woke up without being able to talk, read or write. I got aphasia.
These 8 months have shown me a new life, new experience, new lights to the bigger world outside, and to the inside of my brain and my soul.
Join me on my way back to life and work.
This is my journey.
This is my story.

🤓 Live Dev Building an XrmToolBox Tool!

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!

Building tools for XrmToolBox is fun, easy, and rewarding.

Will be ultra-hands-on! Set up a new project, wire up the tool, the logic, use features of the XrmToolBox dev, use my share controls for the Dataverse platform, and our collective ingenuity.

🧐 Let’s Build a Dataverse Plugin Base Class!

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.

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.