Control Add-ins Supercharged: Development and production build tasks

  • Post comments:2 Comments

I’ve been absent for a while – sometimes it’s difficult to find time for blogging even when I want it. Anyway… here’s the last post in the introductory series of posts that explain my NAV TechDays 2019 demos. In this code example, I explain the difference between typical development and production build configurations, and I show how to configure gulp accordingly.

To check the code example, and to read the detailed explanations of it, jump over to https://github.com/vjekob/supercharged_01/tree/08-gulp-build-prod

(more…)

Continue Reading Control Add-ins Supercharged: Development and production build tasks

Control Add-ins Supercharged: Babel

  • Post comments:0 Comments

After a short absence, I am back. The next lesson in the Control Add-ins Supercharged series I am introducing Babel. "Babel is a JavaScript compiler", says babeljs.io. So, what's the…

Continue Reading Control Add-ins Supercharged: Babel

Code annotations in AL – Please, don’t!

  • Post comments:16 Comments

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.

(more…)

Continue Reading Code annotations in AL – Please, don’t!