mfp: Developing Solutions in a Shared AOS Development Environment

[Blog bot]

Источник: http://blogs.msdn.com/b/mfp/archive/...vironment.aspx
==============
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.




==============
Источник: http://blogs.msdn.com/b/mfp/archive/...vironment.aspx

[fed]

Quote:

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).

Кто-нибудь знает, в лицензировании DAX2012 сделали какие-нибудь послабления, разрешающие каждому разработчику ставить отдельную инсталляцию AOS ? Просто раньше, с одной лицензией разрешалось ставить три инстолляции - Рабочую, Отладочную, Разработческую. Что, в общем, не позволяет больше двух разработчиков иметь в схеме Майкла.

[oip]

Так вроде бы уже давно в лицензии на Акс такого ограничения нет. Когда-то действительно была фраза:

Quote:

The Licensee shall have the right to make copies of the Program for the following purposes only: 1) copies for archival or backup purposes, 2) one (1) copy for development and test purposes

Потом была вот такая редакция (еще во времена 4.0):

Quote:

You may make multiple copies of the software for backup and testing purposes, so long as such copies are not used in production. Your backup copies may be hosted by a third party on your behalf.

Сейчас действующая редакция для 3.0 - 2009 такая:

Quote:

You may make multiple copies of the software for backup, development and testing purposes, so long as such copies are not used in production and the development is for your internal use only. Your backup copies may be hosted by a third party on your behalf.

Для 2012:

Quote:

You may make multiple copies of the software for backup, development and testing purposes, so long as such copies are not used in production and the development is for your internal use only. Your backup copies may be hosted by a third party on your behalf. You may use copies only to create instances of the software.