If you use Team Foundation Version Control, you have several ways to control whether multiple developers can work on same objects simultaneously. You normally want that, because developers often need to change a common file (a class, a configuration file and so on) and waiting for each other would cause unnecessary delays. But it’s not …
Continue reading ‘Locking in Team Foundation Version Control’ »
I already posted an article about the same thing some time ago: Moving a model to another layer. The difference is that it was about Team Foundation Server, but this time I needed to move a model to another layer while using MorphX VCS. MorphX VCS doesn’t support synchronization, therefore my original approach can’t be …
Few days ago my night build of a Dynamics AX 2009 application stopped working correctly. Some objects were missing in the built layer, which of course caused many compilation errors. It occurred that data were correctly obtained from version control, but the Combine XPO Tool (CombineXPOs.exe) couldn’t process them. (If you’re not familiar with that, …
An opinion I encounter relatively often is that a disadvantage of isolated development environments of Dynamics AX is in the fact that if one developer forgets to include an object in version control, the application doesn’t work and doesn’t compile in other development environments. So I’ll probably surprise many people by the statement that I …
Dynamics AX handles text localization by using a label ID (e.g. @SYS1234) in code and metadata; the real text is looked up then based on user’s language. .NET developers may recall localization resources and satellite assemblies and it’s indeed a very similar principle. There are few changes in Dynamics AX 2012 regarding labels, mostly because …
