Getting Ready for Development with Microsoft Dynamics AX 2012 - Part Three: Approach

Back in April, I last wrote in this series about training around getting ready for development with Microsoft Dynamics AX 2012. In that article, I left you with the fact that we will see customers, partners and Microsoft using more and more of the stack for achieving business needs through development.

Continuing down this series of articles, I wanted to now focus on approach. This can be a wide, deep topic that could most likely take an entire book to cover - possibly even several books depending on context and audience. What I want to achieve with this one article is to stress the use of common sense.

I recently wrote an article for the official Dynamics Community, that I would like the preface the content of this article with. That preface is, "Just because you can, doesn't mean you should."

For the developers and development managers out there, I would follow up on that theme to point out that there are some really great options in development around AX 2012 with C#, .Net, Services and Eventing. These are all great things and the right direction for taking AX technically to the next level. However, we have to use common sense in how we design and develop.

What I'm speaking from at this point is not the ISV level of development, which deserves a different article altogether. The focus here is for the customer implementation project. This is for the VAR or customer that is trying to slay that ultimate dragon ...