What is ALM?
As always, it’s an acronym. ALM means Application Lifecycle Management and many texts about ALM are available; white papers, articles, blogs, how-tos… But in my subjective it means:
Continue reading “ALM a la Rapp – Evolve Power Platform delivery”Keep track of everything we need.
/Mr. Rapp
Don’t track things we can generate.
Generate everything automagically.
The Environment Variables feature became officially released a year ago, probably when I was “off the grid” last year. I sort of missed that… but it’s here now anyway.
It’s like system settings, and is now supported by the core Power Platform. We don’t have to build anything for that anymore.
Continue reading “A few requests for Environment Variables”
During the Christmas holiday, I used my time off to explore the integration between Power Apps and GitHub.
I started to explore this new feature because I wanted to see changes to the code. I mean real code. There is no way to easily see the code… Well, Power Apps is a no/low-code as we know, so I also know we should not want to see code… But I do. I have to.
Continue reading “Power Apps Studio and GitHub 🚀”
Read all about this new tool utilizing the Power Apps Checker API here: https://powerappschecker.com
Continue reading “NEW Release: Power Apps Checker for XrmToolBox”
My recent article Case closed: Managed or Unmanaged solutions in Microsoft Dynamics 365 / CRM received a lot of attention, and sparked writers, podcasters, tweeters and commenters around the world to give feedback, yell at me, agree with me, or simply continue the discussion both publicly and privately.
I have received virtual hugs and probably lost quite a few followers.
I really enjoy following and participating in the discussion, and one comment I got today from Anthony Ellis (read it here) inspired me to write a follow-up article. So here it goes.
Continue reading “Managed or Unmanaged solutions – a hot case still slightly open”
If you have problems shifting gears in your car, you don’t call Volvo to say “Hey, I don’t like how this gear shifting thing works, so I’m just going to use reverse and drive backwards from now on.”
What you probably do is call them to say “I’m having trouble shifting, you need to fix the problems or show me how to use it properly.“
Ever since Microsoft introduced the Solution platform with Dynamics CRM 2011, there has been an ongoing and never ending discussion about whether to deploy managed or unmanaged solutions.
I can’t say I can end the discussions or solve all problems. But I will try to convince you – there is no discussion.
Continue reading “Case closed: Managed or Unmanaged solutions in Microsoft Dynamics 365 / CRM”
If you want the full story – these are the articles describing the background and technology behind our tools:
Part I – Background and how our DevOps tools evolved before we knew about it
Part II – Automation of the build and deploy process using custom VSTS Build Tasks
Part III – Demo of complete build and release definitions taking you from A to Z
Part I – Background and how our DevOps tools evolved before we knew about it
Part II – Automation of the build and deploy process using custom VSTS Build Tasks
Part III – Demo of complete build and release definitions taking you from A to Z
After the first two articles we have now got a handful custom VSTS Build Tasks to help us take the build and deployment automation all the way. This final article demonstrates how we do that with VSTS builds and releases. Finally raising the questions of why we did all this and where to go from here.
Below is a sample of a full build process that not only builds and packs a new CRM solution, but updates the individual assemblies and webresources in DEV environment, exports solutions and data, and then publishes the files exported from DEV together with Shuffle Definitions and Package Definition, which is the resulting build artifact.
Continue reading “Build and Deploy Microsoft Dynamics 365 projects using VSTS – part III”
