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

August 21 2011

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.

About Brandon George

Brandon George is a Microsoft Dynamics AX MVP, and President, America's Region, for Hillstar Business Intelligence. You may recognize him from his retired blog or his new BI focused blog Brandon brings hands-on implementation and customization experience in Software Development, Database Design, and SQL Server and leads a team that is charged with helping clients put their data to work.

He has extensive experience in information systems including X++ programming, systems analysis, systems design, configuration, and project deployment. His diverse background in information and business systems gives him a great capacity to interact with people from various business areas and levels. He has outstanding analytical, problem solving, and communication skills as well as proven ability to help people understand complex issues. 

Brandon has worked on numerous large scale implementation projects for Microsoft Dynamics AX and MicroStrategy BI.

His commonly used skills include, but are not limited to:

  • Microsoft Business Solutions and .NET Framework knowledge
  • Microsoft Dynamics AX and MicroStrategy BI hands-on implementation experience
  • Systems architecture and design
  • Applications development
  • Database design
  • Project Management
  • User Training

You can always feel free to email directly at:

More about Brandon George


mfp's picture

I wholeheartedly agree. The purpose of the model driven development in AX is to enable developers to focus more on the domain/business value and less on technical aspects. In AX 2012 the integration with the .NET stack is almost seamless, this means the .NET world is a lot closer than in previous releases and thus in some situations the better choice. You even get deployment and layer-based customization capabilities to your .NET projects. However, you shouldn't default to use .NET just because you can. In some cases it will be the right choice, in others it won't. The same line of thinking also applies to AX based development - in some cases it is preferable - but not always. Also, you must appreciate that certain development scenarios in AX are available in Visual Studio - and still offers the ability to focus on domain/business value. So even if you are a seasoned MorphX developer you should embrace Visual Studio - for example when creating reports.