One month without new posting. But not because I wasn't working for this blog ;-) ...
I was never a fan of the BC.Net and I always hoped that Microsoft would fully integrate the WCF and so fully integarte Ax into a SOA architecture. With Dynamics Ax 2012 it looks like Microsoft did a great move in this direction.
Some years ago I worked on a .Net SOA framework for a French bank that was pretty similar to the Spring-framework which did not exist for the .Net framework at that time. When a colleague presented the Spring.Net framework 2007 (thank you, Bruno) it was first quite frustrating, because this framework did exactly the same as the one I was working on but much better, with much more flexibility and was more reliable. For me it is still the best business framework I know and its SOA approach makes it a perfect fit with Dynamics Ax 2012. Spring.Net is not only a perfect fit because its technical arguments, but also because millions of well skilled Java developers are very quickly operational on this framework because the Spring.Net API is nearly identical with its brother from the Java-platform (and reciproke, of course).
As you can see there are a lot of arguments to do a POC, so that Spring.Net becomes a serious alternative when integrating Dynamics Ax 2012 in a SOA architecture. That's why I started a new project on Codeplex and blog the next months on this POC.
Feel free to participate by contributing code or ideas ;-)
