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.