Thanks to everyone who watched my live stream today! The audience wasn't big, but it's a very narrow topic, not of broad interest. Still, I am glad I got a…
Yesterday, thanks to @sforkmann and his blog at navision-blog.de, I have learned of the existence of Statical Prism. I’ve given it a try today, and I am pretty happy –…
The world needs to move ahead. The technology advances. Who doesn’t want to keep up with the progress, stays behind. That’s how it has worked since the dawn of civilization.
I can’t know the exact reasons why Microsoft has decided to stop support for the Classic client with NAV “7”, but I can offer my view and position on why I believe this was absolutely necessary.
Yesterday, during a coffee break at the What’s New in Microsoft Dynamics NAV 2009 Technical for Application Consultants training in Vilnius, Lithuania (a fabulous place, by the way), a discussion arose around the destiny of the Classic (or C/SIDE) client in NAV. Some participants stated that “it’s never going to go away” because “Microsoft would not dare shutting it down”.
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.
Last week I delivered the C/SIDE Development course for partner community in Zagreb. As always, questions abound afterwards. Today, I’ve got a question from an attendee: “What’s the best way to print a report in multiple languages?”.
Up front: this is NOT a technical post. It IS about technical solution, but it is primarily about design, usability, standards and best practices. I’ll plain ignore the fact that it does use a few C/SIDE or C/AL references, so please, do likewise 😉
(I said this because I kind of swore not to C/AL around this blog anymore, but again – sometimes I just have to do it.)