Just blogged π’: Early-Bound Classes in .NET 4.6.2 and 6.0.
Love .NET strong types in Dataverse / Dynamics 365? Fan of generating Early-Bound Classes? But do you also want to use them in .NET 6.0 and beyond?
Using the same generated classes in in Plugins (= .NET 4.6.2) and outside, like in Azure Functions (>= .NET 6.0) is now a breeze.
See https://automatevalue.com/blog/early-bound-classes-for-net-4-6-2-and-6-0/
Power Platform Advisor
Microsoft Power Platform Advisor with over 25 years of experience in IT with a focus on (marketing) automation and integration.
Helping organizations with scaling their business by automating processes on the Power Platform (Dynamics 365).
Expert in Power Platform, Dynamics 365 (Marketing & Sales) and Azure Integration Services. Giving advice and strategy consultancy.
Services:
– Strategy and tactics advise
– Automating and integrating
A daily newsletter on automation and eliminating friction
I see your comment. And I see AI fingerprints all over it. You know the ones where you think: Bro... did you even read my post? π I get it. We want engagement. We want the algorithm to give us more eyeballs. But fake engagement is still fake. Hereβs what happens when...
Abstract the abstraction π€―. .NET devs, we love our patterns... maybe too much. For a simple CRUD app, I've seen: Repositories β because obviously we can't query directly, that's too mainstream UnitOfWork β like transactions, but now with extra ceremony Services β...
Just blogged π’: Building a ServiceClient Factory for Multi-Tenant Dynamics 365 / Dataverse Apps Struggling with multi-tenant Dynamics 365/Dataverse apps in Azure? Creating a ServiceClient factory that makes managing connections easier! π...