πŸš€ Just moved from raw DLLs to full-blown Plugin Packages using Power Platform Tools in Visual Studio?

This blog is your complete step-by-step guide, from project setup to deploying and debugging in Dataverse, with real screenshots and code.

πŸ”§ No more manual plugin registration chaos.

πŸ’¬ Curious, are you still deploying DLLs manually or gone full package mode?

πŸ‘‡ Drop your setup in the comments!

#PowerPlatform #Dynamics365 #Dataverse #PluginDev #XrmToolBox

http://mytrial365.com/2025/06/26/moving-beyond-dlls-creating-plugin-packages-with-power-platform-tools-for-visual-studio/

Moving Beyond DLLs: Creating Plugin Packages with Power Platform Tools for Visual Studio

In a previous post, we explored the evolution of plugin development in Dynamics 365: We compared the legacy DLL approach to the modern Plugin Package model, highlighting benefits like better ALM, d…

My Trial

🚨 Plugin Developers, it’s time for a reality check!

Still deploying your Dynamics 365 plugins the old-school DLL way? 🧩

πŸ‘‰ There’s a better, cleaner, ALM-friendly way to do it. If you're serious about DevOps, versioning, and scaling your Power Platform apps this shift is non-negotiable.

πŸ’¬ Curious what others think.

#PowerPlatform #Dynamics365 #DevOps #PluginDevelopment #XrmToolBox #MicrosoftDataverse #SolutionArchitecture #ALM #PluginPackage #CDS #DataverseDev

http://mytrial365.com/2025/06/19/plugin-solution-architecture-in-dynamics-365-dll-based-vs-plugin-package-based-approaches/

Plugin Solution Architecture in Dynamics 365: DLL-Based vs Plugin Package-Based Approaches

As the Dynamics 365 and Power Platform landscape evolves rapidly, so does the way we extend the platform using custom code. One significant shift is the movement from traditional DLL-based plugin d…

My Trial

Don't even bother with the #PowerPlatform Admin Center security role editor anymore.

Use this new _n.RoleEditor in #XrmToolBox, to see 33 rows instead of 3 in one screen. Plus tons of powerful features for viewing and editing the intricate details of #Dataverse security model.

3 examples of how people confuse #PowerPlatform UI layer as a valid security boundary:

🚫 Assuming users won't see #SharePoint list data via other means than the Power Apps UI.

🚫 Thinking that the use of #XrmToolBox tools is "hacking" your way into the #Dataverse environment.

🚫 Publishing #PowerBI reports with a semantic model that contains information that should be hidden from users.

Read more: https://www.perspectives.plus/p/ui-layer-is-not-security

So you think UI configuration can deliver data security

Low-code developers repeatedly fall victim to thinking that "what you see is what the user can access".

Perspectives on Power Platform
@underthoughtica if it’s built on #Dataverse have a look at #XRMtoolbox - Xrmtoolbox.com. Specifically, Metadata Document Generator which will output the tables and fields into excel for you.
There may be other useful tools in Xrmtoolbox (I usually find something a week after I needed it!)
@molecat Have you seen XrmToolbox? There are a few neat tools in there to unpick security roles. #XrmToolbox #MicrosoftDynamics

Contributing quick bug fix for #XrmToolBox environment variable manager.

https://github.com/MscrmTools/MscrmTools.EnvironmentVariableManager

#github

GitHub - MscrmTools/MscrmTools.EnvironmentVariableManager: an XrmToolBox tool to update Dataverse environment variables

an XrmToolBox tool to update Dataverse environment variables - GitHub - MscrmTools/MscrmTools.EnvironmentVariableManager: an XrmToolBox tool to update Dataverse environment variables

GitHub