5

June 10, 2011 in Blog, Dynamics AX by Amer

The Use of Visual Studio .NET in the New Microsoft Dynamics AX 2012

Developing applications is now easier and faster in the new Microsoft Dynamics AX 2012 than its earlier versions. .NET developers who are familiar with Visual Studio .NET will be comfortable with developing Dynamics AX applications although Dynamics AX has its own IDE which called MorphX and its own programming language with is X++.

This image shows the Dynamics AX AOT (Application Objects Tree), one of the MorphX IDE objects that Dynamics AX developers use to navigate through programming objects like Forms, Reports, and X++ Classes:

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

With Microsoft Dynamics AX 2012, you can view that AOT in the Microsoft Visual Studio 2012:

Dynamics AX 2012 Applicatoin Explorer in VS.NET

Proxies

Microsoft Visual Studio 2010 now creates proxies internally to support interacting with Microsoft Dynamics AX 2012 X++ classes, tables and base enums. By creating those proxies, developers will interact with Dynamics AX objects in C# and VB.NET exactly as if they are interacting with it in X++. After the proxy is created, that type is available as a strong type and features such as IntelliSense are available. For example, table fields and X++ methods are now exposed to be used in C# with one click. The created proxies are using .NET business connector internally to connect to the Dynamics AX objects.

The following pictures speak quietly how you can access and interact with Microsoft Dynamics AX 2012 objects from within Microsoft Visual  Studio 2010:

Adding Visual Studio Project to the Dynamics AX 2012 AOT

Visual Studio Project inside Microsoft Dynamics AX 2012 AOT

Adding a Dynamics AX 2012 object to the VS 2010 Creates an Internal Proxy

 

The CustTable Appears in the Solution Explorer. You Can Now Use the Dynamics AX CustTable Methods, Properties and Fields!

Share this article:

5 Comments to “The Use of Visual Studio .NET in the New Microsoft Dynamics AX 2012”

• Waqas
  June 12, 2011 at 3:49 pm

  Visual Studio .NET Usage With The New Microsoft Dynamics AX 2012

  http://waqasb.blogspot.com/2011/06/visual-studio-net-usage-with-new.html

  Reply
• Jehanzeb Javeed
  June 22, 2011 at 6:28 pm

  It is looking nice but any idea how much time Visual Studio IDE is taking to loading/saving objects from AX AOT, in AX 2009 the Enterprise Portal Developer Tools for Visual Studio was crashing from VS IDE and had very slow response with AOT may be due to .Net Business Connecter.

  Reply
  • Amer
    June 22, 2011 at 9:10 pm

    Thanks Jehanzeb

    I agree with you about the perforamance of the AX2009.. it has a lot to do with the hardware specs of course.. but you still cannot get the perfect spead even if you havethe best specs ever though.. thats true.

    For the AX2012, calling AOT objects from the VS.NET and saving changes in the AOT from the VS.NET is a way faster than AX2009. I did notice that myself. I’m sure you will notice it if you tried it:).

    Reply
• ajnar
  August 3, 2011 at 2:57 pm

  Hi, don’t know where else to ask as the communities dont seem to have an answer

  I’m trying to add a new user control to the EP on the ax 2012 virtual
  But after creating the table and dataset in ax aot, i can see it in the drop down list for the datanames of the new datasource i am adding
  however when i select it i get an error

  Exception occured on the metadata service on the client or the server
  Exception of Type -
  Microsoft.Dynamcis.Ax.Services.XppBridgeException was thrown
  
  Any ideas?

  Reply
  • Tommy
    January 3, 2012 at 9:50 am

    HI ajnar

    I’ve had similar error in AX2012 after deploying a report in SSRS. If you look in the EventViewer on the server you will most likely find a entry regarding this isssue. In my case there where a line whith the error “Query execution failed for dataset” which maked me look further into my data provider class.

    I found out that there was a call to write an entry in the event log, and after uncommenting this line the report worked perfectly.

    Therefore the conclusion to the error “Microsoft.Dynamcis.Ax.Services.XppBridgeException” was that the acount execution the report didn’t have the nessesary rights.

    My advise to you is to check that the acount running the EP has the nessesary execution right.

    Hope this helps you

    Reply