This is a prominent and frequently used form in the developer workspace – so shouldn’t it be sleek and user friendly?
Here is an annotated screenshot of the final result (click the image for a large version). What do you think?
Sometimes the value added by a garage-project becomes so obvious to everyone, that it must be productized. This is an example. This was literally the last developer feature that made it into AX 2012. Working in an environment where last minute changes to scope is possible despite the project’s (huge) size and extensive engineering processes is another thing I love about my job.
The development training has just been made available for AX 2012. Here are the courses:
The course material is available on PartnerSource.
Today we announced the public availability of Microsoft Dynamics AX 2012.
Microsoft Dynamics AX 2012 empowers people to anticipate and embrace change, enabling businesses to thrive.
A powerful foundation that is purpose-built for five industries: manufacturing, distribution, retail, services, and public sector, along with comprehensive, core ERP functionality for financial, human resources and operations management. All packaged in a single global solution thus giving customers a rapid time to value.
Agility through a set of unified natural models that serve as a library of business processes reflecting real-world situations. This enables customers to easily modify their organizations and processes to meet their changing business needs.
Simplicity through an easy-to-use solution offering access to information that is relevant to the work at hand. The familiar Microsoft Office user interface drives adoption and the enhanced business intelligence (BI) capabilities help customers uncover fresh insights that can lead to faster and more informed decision making.
For more information see:
One often asked question is how to configure a development with multiple developers. The options span from having a silo for each developer where they host AX, AOS, SQL, etc. locally, to a shared setup where each developer only needs an AX client. These options can be combined with the use of a version control system, such as Team Foundation Server or MorphX VCS. Further the capabilities and infrastructure requirements are quite different among the options.
To describe the options and their capabilities Microsoft has published: Microsoft Dynamics AX 2012 White Paper: Developing Solutions in a Shared AOS Development Environment
The first paragraph of the white paper is:
Developing for Microsoft Dynamics ®AX is best done in an environment where each developer has a full Microsoft Dynamics AX installation that runs on a single box. The developer artifacts are synchronized by using one of the supported version control systems in Microsoft Dynamics AX, and solutions are produced by running a build of the sources in the version control system (VCS).(Emphasis mine).
The rest of the white paper is describing consequences of using other configurations, such as a shared AOS. While there are multiple desirable traits of a shared environment, for example simpler infrastructure and the ability for developers to quickly change project, these benefits come at a cost. I encourage you to make an informed decision when selecting your configuration based on your needs and this whitepaper.