If you get multiple entries when hovering the mouse over a variable name in the Microsoft Dynamics NAV 2015 debugger – you are out of luck.
The debugger does not perform a lexical parsing of the source, so it will just search the variable space, and in cause of multiple hits, it will show them all.
So when you hit something like this, you got to perform your own parsing – In my case, this came from a piece of code that used the WITH <?> DO statement.
So this picture is circulating on Twitter – a simplification of the Dynamics logos, nice -But I do have one question? What is “Microsoft Dynamics CS” ?
A new product in the family ?
Just a logo for CustomerSource ?
A typo, should have been Dynamics C5 ? (Correct answer, thanks you internet)
Just a mock up added to make it a even 6 and a nicer layout ?
Tweet me @eHougaard if you got a suggestion ?
Now that the summer is over, it’s time to read a good book. Here are a couple of recommendations on the subject of NAV development.
This is one of the best no-nonsense books on NAV development you can get. Read it, understand it, and you’re ready to development with Dynamics NAV 2015. Dave has been using NAV since it was called Navision and Navigator – he knows the pedigree of the system and its history.
The book takes you through all the normal aspects of developing a customer solution with NAV – and uses best practice and sound patterns in all the solutions suggested.
Each chapter concludes with a small questionnaire that covers the content of chapter.
This book is one of the essentials for every NAV developer – I recommend it highly !
Get it here
So now you can develop in NAV, then it becomes important to do it correctly. And one way is to use design patterns. My good friend Mark Brummel is preaching about them every chance he gets, and with good reason, reusing the way NAV is already working is one of the most important paths to a successful project.
Pick up his new book in October on Design Patterns – I know I will.
And Marks old book on NAV application design is still a good source of knowledge, don’t let the “2013” title fool you, its still very relevant for 2015 (and 2016).