Testing, testability, and all things test
Okay. There has been a lot of "long time no see" intros to my posts on this blog in the past, but never this long. So - looooooong time no…
Okay. There has been a lot of "long time no see" intros to my posts on this blog in the past, but never this long. So - looooooong time no…
There is a cool new extension out there for AL developers that you should really check out: AL Pragma Explorer. The extension is almost as amazing as the work behind it, because even though this extension is published under my publisher name, it’s not really just mine. This was a team effort of my group at the BC TechDays 2022 preconference workshop, and I am so proud that we actually managed to pull this thing off.
So, here’s the story.
(more…)
One of good practices of writing C/AL Code for Microsoft Dynamics NAV since the dawn of civilization was annotating (commenting) code changes. If you are not sure what I mean by that, this is what I am talking about:
While standards varied about > vs +, or < vs -, or what the annotations should include, there was absolute consensus that annotating changes is an absolute must.
And it was a must. It was such an important rule that everyone followed it without questions asked. In my career, I’ve seen one or two situations of somebody changing or deleting a line of code without leaving any comment, and I’ve seen quite a lot of code, believe you me. It was that important.
It was that important in fact that it was one of the first things developers learned when they signed up for the job, and it was one of the rules they all followed from their first day.
There is a particular programming language feature that I've always missed in AL (and C/AL for that matter): interfaces. I've dreamt about it, then blogged about it, then finally created…
Now that you are done through this mouthful of the title, you may recognize that itβs the method you invoke when you want to run a control add-in trigger in…