So, here it is, given as-is, with no guarantees or strings attached, just the plain content for you to see if you can make any sense out of it.
Now my to-do list has grown quite big with the stuff that I want to blog, and it includes presenting and explaining most of the concepts I showed in my presentation. So, keep your fingers crossed that I find just enough time to blog about all those small things that have found their way into my presentation, but never into real blog posts that take them inside out and explain in-depth what they are and how really they work.
Of course, you are still free to use any of this in any real, or unreal life scenarios.
Many cool things often go undocumented. I’ve just stumbled upon one of those, and it comes in handy to close this year of blogging.
Imagine this situation: you have a server-side .NET object, that you want to pass on to the client. With the .NET System.Windows.Forms-based objects, you have to make the object serializable, deploy the object to the client-side Add-in folder, and then set the RunOnClient property on the C/AL variable to Yes.
Unfortunately, it is going away, and quickly. Maybe it wasn’t too obvious at first, because Microsoft never actually said explicitly that “Classic client is going to be discontinued”, but if you read the latest Statement of Direction for Microsoft Dynamics NAV, it’s there.