web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics AX (Archived) / AX 2009, BusinessConne...
Microsoft Dynamics AX (Archived)

AX 2009, BusinessConnector and VisualStudio

(0) ShareShare
ReportReport
Posted on by Jerzy Kopinski 145

Hi all,

As a quite begginer in developing apps for  Dynamics AX 2009 I have no idea how to built a developing environment to develope apps using .Net BusinessConnector. So, please, forgive me the following questions:

1. Can Visual Studio 2010 or 2012 be used to write apps for AX 2009 with .Net BsuinessConnector usage? I founded only info about VS 2008.

2. Is there any trial version of AX 2009 that could be downloaded and installed localy to develope software and test it?

3. What is difference between Bizz Talk  and .Net BusinessConnector from developing point of view?

I would be very grateful for any help.

Jerzy

 

*This post is locked for comments

I have the same question (0)
  • Verified answer
    Martin Dráb Profile Picture
    Martin Dráb 239,634 Most Valuable Professional on at

    1. Sure, it's just an API.

    2. Something is available through Technet/MSDN subscription, but I don't know the current situation.

    3. Well, these are two very different things. Are you interested in something particular?

  • Jerzy Kopinski Profile Picture
    Jerzy Kopinski 145 on at

    Hi Martin,

    Thanks for your answer. As to the p.3 I have to write external app, or rather external interface for some application. Of course business logic will be a part of Dynamics logic. I think that .NetBusinessConnector usage would be the best solution. However I read somewhere that BizzTalk could be used to accomplish the same objective. May be I am wrong. So that is why I asked the question.

  • Martin Dráb Profile Picture
    Martin Dráb 239,634 Most Valuable Professional on at

    Business connector is basically a special AX client and API, allowing you to connect to AX and send some commands to it. BizTalk is an independent server in the center of enterprise communication transforming data between various applications. Each application has to implement just a single connector to BizTalk and not a separate connector for each application it wants to communicate with.

    BizTalk knows nothing about AX, the advantage is that there is such a connector to Dynamics AX (as an AIF adapter).

    Business Connector has some limitation - e.g. it needs to be in the same domain. AIF, on the other hand, is intended more for data transfer than any interactivity. Based on your requirements, you can choose Business Connector, AIF (including, but not limited to BizTalk) or a custom service.

    Finally your application may talk to a BizTalk server communicating through a webservice with IIS, which connects through Business Connector to AX AOS in internal network. :)

  • Verified answer
    Jerzy Kopinski Profile Picture
    Jerzy Kopinski 145 on at

    Thanks again Martin for your comprehensive and helpful replaying. I see that I should explore AIF. Could you, please, explain what do yout think talking about custom service as an option instead of BC and AIF?

  • Martin Dráb Profile Picture
    Martin Dráb 239,634 Most Valuable Professional on at

    You may want to bypass BC limitations and rather communicate through WCF service (or something) and in the same time not to bother with all the AIF stuff like document classes etc. Then you can create your own WCF service in Visual Studio that will run on IIS, your application will communicate with the service and the service will talk to AX through Business Connector.

    If it sounds strange, notice that the same architecture is used by AIF for webservices.

    AX2009 doesn't have any special support for these services, but AX2012 does and call them custom services. Although they work differently (e.g. AOS hosts WCF services itself so IIS/BC is not needed), it's worth to be aware of them and try to design AX2009 services to be easily upgraded to AX2012.

  • Verified answer
    DHB Tatva Profile Picture
    DHB Tatva 939 on at

    Hi Jerzy,

    1) AX 2009/2012 can use only .Netframework 3.5 only....4.0 is not supported (till now).

       (On VS 2010/12...select 3.5 or less Framework to get AX installed templetes)

    2) BizTalk is an Ultimate MiddleTier Sever which can Integrate vast no. of softwares, services, web services...thro various inbuilt/custom/third party adapters.

          a) BizTalk 2006R2/2009 + AX 2009 have an Inbuilt BizTalk Adapter.

          b) BizTalk 2010 + AX 2012 are parted...i.e...AX itself has Aif File system (Folder), NetTcp, MSMQ & Http adapters.

     3) .Net BusinessConnector uses Microsoft.Dynamics.BusinessConnectorNet.dll from AX Sdk to develop various applications on Visual Studio.

    Any thing else you need, please let me know.

     

    DHB.

     

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the April Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
CP04-islander Profile Picture

CP04-islander 24

#2
Michel ROY Profile Picture

Michel ROY 14

#3
Jagadabi Profile Picture

Jagadabi 6

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans