When and Why a Hybrid Development Approach Makes Sense for Microsoft Dynamics GP

As I prepare for my journey to the 2009 Microsoft Dynamics GP Technical Conference, where I will be delivering two sessions with my friend David Musgrave, a topic that has surfaced throughout the sample applications we are getting ready to showcase at the event is the use of  hybrid code.

Simply put, in the world of software development, the earth doesn't always revolve around the sun. In fact, in the world of Software Development, there are times when the sun and other planets may need to revolve around the earth. That is, the business solution becomes the center of the Solar system and all resources at your organization's disposal work to make that solution robust and to meet the requirements established by your internal and external customers.

Hybrid application development involves using multiple development tools and techniques to make a solution to a problem a viable one. In the case of Microsoft Dynamics GP development, these development tools involve the use of Microsoft Dexterity, Visual Basic for Applications (VBA), and Visual Studio Tools for Microsoft Dynamics GP. To think that one tool is enough to build an application is simply very limiting in nature - take this from the Microsoft Dexterity developer in me. In fact, as the Microsoft Dynamics GP application suite continues to expand its use of managed code and adapt to changes in technology, using one tool to deliver a solution is becoming near sided.

When you evaluate the potential of customizing Microsoft Dynamics GP, a hybrid development approach will then allow you and your IT development organization to take advantage of the best features ...