Last week at directions Microsoft did a demo where they’ve shown the full solution running as an extension with only the system objects left in C/SIDE, that’s great, right?
In this blog, I’ll share my thoughts on the subject and make you aware of the impact it has.
Over the last few months, Microsoft has been preparing for this move, if you’ve been following the insider builds you might have noticed that they’ve separated the actual application code from the code that interacts with the platform (like codeunit 1), refactored those objects and moved them to the platform range (2000000000).
So why are they doing this? The answer is quite obvious, it’s time for C/SIDE to retire and focus on the modern development tools.
Let’s have a look at the roadmap to find out when C/SIDE’s retirement will become effective:
Next year Microsoft will finalize the C/AL to AL conversion and in 2020 it’ll be VS Code & AL only, which means end of life for C/SIDE.
This doesn’t mean you can’t use C/SIDE anymore with the older versions of NAV and BC, it just means that no effort goes to C/SIDE anymore.
What’s in it for us?
Questions I have:
Even though you’ll be able to take all of your lovely footprint to AL, it’s still really important to adopt a zero-footprint mindset, this saves you a lot of time when merging, upgrading etc.
If you haven’t started with reducing your footprint yet, here are a few tips to get you started: