Microsoft Dynamics AX 2009 White Paper: Using the Version Control Integration with Microsoft Team Foundation Server
One of the topics that a lot of customers need to be really thinking about, and sometimes is not part of the initial project implementation, is Source Control, Version Control --- Control over the development of Dynamics AX objects and projects, the a Version Control System.
Microsoft has a great product, called 'Team Foundation Server'. Team Foundation Server, offers different levels depending on the need of the customer, and is not just a run of the mill VC solution.
If offers planning, control, documentation, BP, guidelines, branching, promotion options, and allows different role types to view a given project or set of projects in the manner best suited, and allowed for them.
With Dynamics AX 2009, you can actually take and make use of Team Founcation Server, with your instance to help gain control and governance over the development and lifecycle of your given Dynamics AX investment.
A very good white paper, that was release this past July, talks in details about this. That is the following white paper.:
Microsoft Dynamics AX 2009 White Paper: Using the Version Control Integration with Microsoft Team Foundation Server
The above image shows the Object Lifecycle when making use of TFS integration within Dynamics AX.
So this offers an amazing amount of power. The only draw back, for smaller shops, is the fact that each developer machine, must have their own AOS. So if you have 10 developers, then that's 10 AOS licenses, you will need.:
Developer Machines
Each developer machine should have:
There are other options, but for a shop that wants to get the most out of their investment for Dynamics AX, even having an AOS per developer, does not cost that much in the scheme of things. When your talking about your enterprise business platform!
That's all for now, check back soon as more to come!
"Visit the Dynamics AX Community Page today!"
Microsoft has a great product, called 'Team Foundation Server'. Team Foundation Server, offers different levels depending on the need of the customer, and is not just a run of the mill VC solution.
If offers planning, control, documentation, BP, guidelines, branching, promotion options, and allows different role types to view a given project or set of projects in the manner best suited, and allowed for them.
With Dynamics AX 2009, you can actually take and make use of Team Founcation Server, with your instance to help gain control and governance over the development and lifecycle of your given Dynamics AX investment.
A very good white paper, that was release this past July, talks in details about this. That is the following white paper.:
Microsoft Dynamics AX 2009 White Paper: Using the Version Control Integration with Microsoft Team Foundation Server
The above image shows the Object Lifecycle when making use of TFS integration within Dynamics AX.
So this offers an amazing amount of power. The only draw back, for smaller shops, is the fact that each developer machine, must have their own AOS. So if you have 10 developers, then that's 10 AOS licenses, you will need.:
Developer Machines
Each developer machine should have:
- Microsoft Dynamics AX 2009 Developer installation (with AOS)
- Microsoft SQL Server (local or remote)
- Local repository folder
- Visual Studio Team Explorer (optional)
There are other options, but for a shop that wants to get the most out of their investment for Dynamics AX, even having an AOS per developer, does not cost that much in the scheme of things. When your talking about your enterprise business platform!
That's all for now, check back soon as more to come!
"Visit the Dynamics AX Community Page today!"
Labels: Dynamics AX, Dynamics AX 2009, lifecycle, Microsoft, Team Foundation Server, TFS, VCS, Version Control, Whitepaper
posted by brandon | 9:26 AM
3 Comments:
TFS really sounds very tempting, but I still do not see how implementation partners can use it efficiently ...
Using TFS, they would need one AOS per developer and _per_customer_project_, which really implies a LOT of administration ...
Do you know about AX implementation partners (not ISVs) using TFS?
Agreed Annette, I have been resisting this configuration exactly for that reason. This configuration is not the best for shops that bring in consultants, consultants that are at several clients. I was one of the presenters at Convergence where we talked about source code control. At that session, one could observe that there are still many different methodologies used for storing and promoting code. I was hopeful that the MS guys that actually develop and implement AX would have been in our session, but they didn't show up.
Hi,
I have only 3 AX developers who will work on AX development. I have installed AX 2009 with AOS on our server and AX client application on each developer machine. Now I have implemented the integration between TFS and AX 2009 sharing the single AOS instance and AX DB(SQL server) using installing Team Server(ID) on that server between all 3 developers.
Is this thing will work that to share a single AOS with single AXDB associated using Team server installation between all 3 devs.?
Please let me know your comments.
/Ashlesh
Post a Comment
<< Home